Specify a document lifecycle that survives parser retries
A retry currently moves a completed document back to processing because delivery events are mistaken for authoritative transitions.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- State machines · Idempotency
Estimated field mix
- System design50%
- Backend30%
- 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 portal extracts metadata from uploaded documents. Product wants a responsive upload flow; security wants parser failures isolated from customer-facing processes.
Setup prerequisites
- Create synthetic upload metadata and a fake processing provider.
- Treat diagrams as proposals; implement only local contract probes.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Define legal transitions and terminal-state behavior.
- Bind processing attempts to one immutable upload generation.
- Reject stale provider completion for a replaced generation.
Implementation constraints
- Express the transition table as executable tests against a small pure model.
Verification to include
- Replay valid completion twice and retain one terminal result.
- Deliver an older generation result after replacement and reject it.
Deliverables
- State model and transition probes
Rollout and recovery
Use the model to gate implementation review; create a new model version for changed semantics.
Value of the work
For the engineer: Practice boundary decisions backed by executable consistency and failure checks.
For the team: Review architecture tradeoffs with explicit assumptions before infrastructure commitment.
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.