Skip to content
Product Lab
Family ManagerSample

A forwarded document becomes a calendar you can trust

Forward a school, camp, sports, or medical document and the agent extracts proposed events, deadlines, and checklists, each with a resolved absolute date. Every proposal becomes an approval card: nothing is added until a parent approves, the governed HITL spine. Approved items are routed to the calendar, then re-read to confirm the write.

Approval cards drafted
128
Routed to calendar
104
Corrected, then approved
16
Denied
17
Source types
5
Governed runs
5
Go deeper

Inspect the loop, end to end

Two detail views open the loop up: how a single forwarded document becomes reviewable proposals, and what the loop learns over time.

The loop

Capture, extract, approve, route

One engine, one loop. Counts are coarse and content-free, the documents, senders, names, and event titles never appear.

  1. Step 1

    Capture

    Documents forwarded to the household address: school, camp, sports, and medical.

    96items

  2. Step 2

    Extract

    Each document is parsed into proposed events, deadlines, and checklists with a resolved absolute date.

    128items

  3. Step 3

    Approve

    Every proposal becomes an approval card. Nothing is added until a parent approves: the HITL spine.

    121items

  4. Step 4

    Route

    Approved items are routed to the on-device calendar, then re-read to confirm the write.

    104items

Sources

Where the documents come from

A coarse mix of forwarded-document source types, closed-enum only, never the document itself.

  • School41 docs · 58 proposals
  • Camp24 docs · 34 proposals
  • Sports19 docs · 22 proposals
  • Medical9 docs · 11 proposals
  • Other3 docs · 3 proposals
Proposals

What the agent drafts

Each extracted proposal is an event, a deadline, a checklist, or a reminder.

  • Events71
  • Deadlines29
  • Checklists18
  • Reminders10
Human in the loop

Approve, deny, correct, and loud failures

The coarse outcome of every approval card. Routing failures are shown, not hidden, an unverified write is never a silent success.

  • Approved88
  • Corrected, then approved16
  • Denied17
  • Routed to calendar104
  • Routing failed2
  • Awaiting you7
Confidence

How sure the extraction was

A coarse high / medium / low band. Only low-confidence proposals nudge mandatory review.

  • High confidence82 · 64%
  • Medium confidence34 · 27%
  • Low confidence12 · 9%
Governed runs

The recent run timeline

Each forwarded document triggers a governed run. Blocked runs (e.g. a source that is not eligible) are first-class, not hidden.

  • SucceededCamp4 cards · 4 routedLow band38s · 4d ago
  • SucceededSchool5 cards · 5 routedLow band31s · 4d ago
  • SucceededSports3 cards · 2 routedLow band27s · 4d ago
  • BlockedMedical0 cards · 0 routedLow band · 4d ago
  • SucceededSchool6 cards · 5 routedMedium band52s · 5d ago

What you can see, and what is hidden

Every projection on this page is redaction-safe by construction. Redaction level: Content-free, ids, counts, and coarse scores only.

Shown

  • Identifiers & counts
  • Closed-enum statuses
  • Coarse quality / resource bands
  • Timestamps & freshness

Intentionally hidden

  • Raw prompts
  • Raw documents
  • Sender email addresses
  • Child / member names
  • Raw trace spans
  • Embedding vectors
  • Free-text feedback
  • Auth internals & secrets

Related in the Lab

Read the story: how Family Manager became the platform's proof app