Classify essential and optional ticketing requests
Recommendation requests compete with reservation checks without any priority policy.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Reliability design
Estimated field mix
- Site reliability60%
- System 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 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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- List request classes and user impact.
- Define allowed degradation per class.
- Keep reservation correctness invariant.
Implementation constraints
- Do not prioritize users by inferred personal traits.
Verification to include
- Classify a reservation and recommendation request.
- Identify a request that must fail explicitly rather than degrade silently.
Deliverables
- Request-class policy.
Rollout and recovery
Review classification before applying limits.
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.