Validate source spans for every extracted material field
The provider returns a supplier address that appears nowhere in the document.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Grounding · Validation
Estimated field mix
- Applied AI80%
- Data 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.
Acceptance criteria
- Require bounded source spans for material values.
- Resolve spans against the exact source version.
- Flag transformed values with their documented normalization rule.
Implementation constraints
- Provider prose cannot substitute for source support.
Verification to include
- Accept a supported normalized date.
- Reject out-of-range spans and invented supplier values.
Deliverables
- Source-grounding validator.
Rollout and recovery
Keep unsupported drafts blocked for review; retain safe failure categories.
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.