Deduplicate concurrent extraction requests without mixing versions
Two upload retries consume duplicate provider budget and occasionally attach the older result to the newer run.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Concurrency · Idempotency
Estimated field mix
- Applied AI50%
- Database engineering30%
- Distributed systems20%
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
- Deduplicate exact document and extractor identities.
- Reject conflicting reuse of an operation key.
- Commit one terminal result and preserve failed-attempt metadata.
Implementation constraints
- Access providers through AiEvaluationProvider with bounded timeout and retries.
Verification to include
- Race identical requests and observe one accepted result.
- Change extractor version and ensure a distinct run.
Deliverables
- Extraction operation coordinator.
Rollout and recovery
Adopt one document type first; retry terminal failures through a new explicit operation.
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.