Define invoice fields with explicit missing and ambiguous states
Empty strings currently mean both absent values and extraction failures.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Schema design
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Represent value, missing, and ambiguous states distinctly.
- Declare required fields before a draft is reviewable.
- Preserve the original textual date and amount references.
Implementation constraints
- Do not guess missing tax or currency values.
Verification to include
- Parse a complete synthetic invoice.
- Represent missing currency and an ambiguous date without invented values.
Deliverables
- Extraction schema.
Rollout and recovery
Version the schema before creating drafts; retain raw synthetic source references.
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.