Choose the read model for pending document status
Product wants frequent status updates, but the proposal polls the external parser on every customer request.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Read models · Authorization
Estimated field mix
- System design50%
- Backend30%
- Real-time 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.
- ABOUND-101 · Translate document-processing expectations into a bounded workload model
- ABOUND-102 · Draw the document trust boundary with authoritative state owners
- ABOUND-103 · Write the decision record for direct-to-storage document upload
- ABOUND-104 · Specify a document lifecycle that survives parser retries
- ABOUND-105 · Design the transactional dispatch contract for extraction work
- ABOUND-106 · Define extraction-provider deadlines and uncertain completion semantics
Acceptance criteria
- Serve status from authorized durable local state.
- Specify freshness and pending-state wording.
- Compare bounded polling and push updates under the assumed workload.
Implementation constraints
- Keep raw parser diagnostics outside customer projections.
Verification to include
- Read one pending and one completed document through the local model.
- Request another tenant's document and verify no provider lookup occurs.
Deliverables
- Read-model decision and scoped contract probe
Rollout and recovery
Prototype the local status route; retain polling until push delivery has a measured need.
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.