One forwarded document, turned into reviewable proposals
A single forwarded document runs through a governed pipeline and becomes a small set of structural approval cards. You see the coarse source type, how many candidates were drafted, each card’s confidence band and human-in-the-loop outcome, and the shared-source match rate — never the document, the sender, or any name.
- Candidates drafted
- 4
- Approved
- 2
- Rejected
- 1
- Shared-source hit rate
- 50%
- Pipeline stages
- 5
- Approval cards
- 4
The approval cards this document drafted
Each candidate becomes a structural approval card. You see its confidence band, its outcome, and the trust facts, a resolved absolute date and a single-use decision token, never the title or the date itself.
- Calendar eventApprovedHigh confidenceResolved dateSingle-use token
- Calendar eventApprovedHigh confidenceResolved dateSingle-use token
- ChecklistEditedMedium confidenceNo resolved dateSingle-use token
- Calendar eventRejectedLow confidenceResolved dateSingle-use token
Approve, edit, reject, dedupe
The coarse outcome of every candidate from this run. Nothing is hidden, a rejected or deduped candidate is first-class.
- Approved2
- Edited1
- Rejected1
- Deduped0
Parse, OCR, extract, candidates
The coarse governed pipeline that turned the forwarded document into candidates, with per-stage status and duration. Stage names are closed-enum, not content.
- 01receiveSucceeded40ms
- 02parseSucceeded210ms
- 03ocrSucceeded880ms
- 04extractSucceeded1.6s
- 05candidatesSucceeded95ms
What the loop learns
See how shared-source matches and role-weighted feedback turn into learned candidates, with eval gates and demonstrated rollbacks.