Prepare a reviewer checklist for ambiguous supplier documents
Reviewers need a consistent way to handle ambiguous dates and unsupported fields.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Low
- Engineering practice
- Documentation · Workflow design
Estimated field mix
- Applied AI100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional procurement team receives inconsistent supplier documents. It wants draft records that staff can review without treating model output as authoritative accounting data.
Setup prerequisites
- Author synthetic text invoices with ambiguous dates, currencies, and line items; use a deterministic provider double.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BEXTRACT-101 · Define invoice fields with explicit missing and ambiguous states
- BEXTRACT-102 · Bind extraction runs to immutable document digests
- BEXTRACT-103 · Validate source spans for every extracted material field
- BEXTRACT-105 · Prevent document text from overriding extraction policy
- BEXTRACT-104 · Check line-item arithmetic using exact decimal rules
- BEXTRACT-106 · Deduplicate concurrent extraction requests without mixing versions
- BEXTRACT-107 · Reserve extraction cost before processing a document batch
- BEXTRACT-108 · Preserve corrections as append-only reviewer decisions
- BEXTRACT-109 · Design a field-level extraction evaluation with abstention costs
Acceptance criteria
- Explain how to inspect source spans and arithmetic discrepancies.
- Show how to request correction without editing source history.
- Document when a draft must remain unresolved.
Implementation constraints
- Do not treat review completion as proof of invoice authenticity.
Verification to include
- Review one supported synthetic invoice.
- Leave an ambiguous supplier document unresolved with a reason.
Deliverables
- Reviewer guide.
Rollout and recovery
Publish alongside the prototype; revise examples when extraction policy changes.
Value of the work
For the engineer: Practice schema constraints, numerical checks, review workflows, and safe model boundaries.
For the team: Produce an inspectable extraction prototype that can reduce manual transcription while preserving review control.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.