Freeze the required check set when a document review run starts
A configuration change adds a checker while a run is in progress, so the completion predicate changes halfway through.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Immutability · Workflow contracts
Estimated field mix
- Distributed systems60%
- Backend40%
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 vendor portal runs format, policy and duplicate checks in parallel. A slow checker blocks completion, while duplicate callbacks can produce contradictory final summaries.
Setup prerequisites
- Create synthetic document identities and three fake check providers.
- No real risk scoring, hiring decisions or candidate execution is included.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Record exact checker identities and versions per run.
- Bind the set to immutable document input identity.
- New configuration affects only new runs.
Implementation constraints
- Use three deterministic fake checks with no capability scoring.
Verification to include
- Start runs before and after a check-set change.
- Finish the older run using its original required set.
Deliverables
- Review-run manifest
Rollout and recovery
Publish frozen manifests before parallel dispatch; retain prior checker versions for replay.
Value of the work
For the engineer: Practice fan-out/fan-in, deadline policies and immutable aggregation.
For the team: Review trustworthy partial-result handling and controllable parallel work.
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.