Ingestion → calendar

One clear event lands. One uncertain event waits.

This route processes a checked-in .eml fixture on the server. It uses a real MIME parser and deterministic policy code, with a deliberately fake extractor standing in for the future local model.

2proposals found

1published automatically

1sent to review

1item after replay

Trace

What the pipeline did

Review ready

1
Received raw email
Avery's field trip and family night
From
office@example-school.test
Envelope recipient
calendar@inbound.family-organizer.test
Attachments
1
2
Parsed and normalized
MIME content became a source record with content and attachment digests.
sha256:dfbce73e28b0630c07be…
3
Extracted proposals
Mock extractor produced evidence-linked structured candidates.
4
Applied policy v1
Opt-in enabled · calibrated threshold 0.98 · direct date evidence and known member required

Automatic publication

Museum Field Trip

Added

Starts: Oct 9, 2026, 8:15 AM
Location: City Science Museum
Calibrated confidence: 0.995
Resolution: Automatic policy

Direct evidence checked

startsAtDate: Friday, October 9, 2026 / Meet: 8:15 AM
endsAtReturn: 2:45 PM
locationLocation: City Science Museum

Exception queue

Family night

Review

Date found: No reliable date
Source phrase: “next Thursday at 6 PM”
Model confidence: 0.97
Calibrated confidence: 0.74

Why it did not auto-publish

Calibrated confidence 0.740 is below the 0.980 threshold.
A required calendar field is missing.
The event date/time lacks direct source evidence.
The proposal has unresolved questions.

Idempotency replay

The same provider delivery was ignored safely.

Duplicate detected: yes. Calendar items after replay: 1.

Calendar projection

The published item is available as ICS.

This local demo feed is generated from the same in-memory publication shown above. It is intentionally unauthenticated fixture data, not a private household feed.

Download demo calendar