Preserve corrections as append-only reviewer decisions
Staff corrections overwrite the extracted values, making later disagreement impossible to investigate.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Auditability · Concurrency
Estimated field mix
- Backend50%
- Applied AI30%
- Database engineering20%
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-104 · Check line-item arithmetic using exact decimal rules
- BEXTRACT-106 · Deduplicate concurrent extraction requests without mixing versions
Acceptance criteria
- Record original value, corrected value, reviewer, and reason.
- Require optimistic revision control for concurrent review.
- Keep source and extractor output immutable.
Implementation constraints
- Review actions must be tenant-scoped.
Verification to include
- Correct a draft and inspect both versions.
- Reject stale revisions and cross-tenant review attempts.
Deliverables
- Correction history workflow.
Rollout and recovery
Enable on draft records first; retain prior review state when a correction fails.
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.