Reserve extraction cost before processing a document batch
A large upload queue can exceed the tenant's configured processing budget.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Cost controls · Transactions
Estimated field mix
- Applied AI50%
- Database engineering30%
- Backend20%
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
- Estimate a conservative per-document reservation.
- Enforce tenant and batch ceilings before dispatch.
- Settle actual usage and return unused reservation exactly once.
Implementation constraints
- Record model, prompt/schema version, timeout, retries, cost, and trace without document text.
Verification to include
- Process a batch within the ceiling.
- Retry settlement and verify no double charge or negative reservation.
Deliverables
- Budget accounting tests.
Rollout and recovery
Start with a small ceiling; pause new dispatch when accounting state is uncertain.
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.