Finalize aggregates only from the frozen required check set
An optional checker finishes quickly and accidentally satisfies a counter-based completion condition while a required checker is missing.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Aggregation · Set invariants
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
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- ABATCH-101 · Freeze the required check set when a document review run starts
- ABATCH-102 · Define pass, fail, unavailable and not-applicable check outcomes
- ABATCH-103 · Bound parallel check fan-out per organization and run
- ABATCH-104 · Dispatch each check through a durable deterministic attempt identity
- ABATCH-105 · Deduplicate callbacks without accepting contradictory check results
Acceptance criteria
- Evaluate completeness by exact required identities.
- Compute aggregate state from validated immutable check facts.
- Reject finalization when required results are missing or conflicting.
Implementation constraints
- Define aggregate output as review status, never an opaque hire/reject score.
Verification to include
- Finish all required checks and produce the expected status.
- Complete extra optional checks while omitting one required check and block completion.
Deliverables
- Aggregate reducer and completeness tests
Rollout and recovery
Enable guarded finalization before publishing results; retain pending state on missing authority.
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.