Propagate request deadlines to downstream work
The client has timed out while its dependency request continues holding a slot.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Cancellation · Resource lifecycle
Estimated field mix
- Backend40%
- Site reliability30%
- Networking30%
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 ticketing service becomes unresponsive during event releases because optional recommendation calls consume the same resources as reservation checks.
Setup prerequisites
- Build a bounded local service and synthetic open-loop workload generator with controllable dependency delays.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Derive child deadlines from remaining request time.
- Abort owned work on cancellation.
- Release capacity even when a double ignores cancellation.
Implementation constraints
- Bound cleanup time and track late completions safely.
Verification to include
- Complete within a shared deadline.
- Timeout an uncooperative dependency and reclaim the slot.
Deliverables
- Deadline propagation.
Rollout and recovery
Default to shorter optional deadlines; retain explicit timeout responses.
Value of the work
For the engineer: Practice overload behavior, admission control, and fair performance experiments.
For the team: Create predictable failure and degradation behavior under declared capacity constraints.
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.