Define pass, fail, unavailable and not-applicable check outcomes
A timed-out policy checker returns an empty findings list, which the aggregator interprets as passed.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Structured validation · Uncertainty
Estimated field mix
- Distributed systems60%
- API design40%
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.
Acceptance criteria
- Use explicit outcome states with bounded structured details.
- Require justification for not-applicable under the declared contract.
- Keep unavailable distinct from an empty successful result.
Implementation constraints
- Reject unsupported fields and prohibit demographic or personality inferences.
Verification to include
- Accept a valid empty successful check.
- Timeout a checker and retain unavailable rather than pass.
Deliverables
- Check-result schema and semantic cases
Rollout and recovery
Deploy result validation before aggregate updates; quarantine incompatible provider output.
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.