Turn the registration forecast into a workload envelope
The launch plan says 'ten times traffic' without a base rate or request mix.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Capacity planning
Estimated field mix
- Performance engineering60%
- Site reliability40%
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 course platform expects a registration deadline spike. Capacity assumptions, escalation ownership, and degradation decisions are scattered across old documents.
Setup prerequisites
- Create synthetic registration traces and local dependency doubles with finite connection and request limits.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Declare arrival range, duration, and request mix.
- Separate new registrations from read traffic.
- Identify unknown forecast assumptions.
Implementation constraints
- Use fictional demand figures and label them assumptions.
Verification to include
- Convert the forecast into a bounded local trace.
- Reject an unspecified multiplier as a complete workload definition.
Deliverables
- Workload envelope.
Rollout and recovery
Review assumptions before capacity testing.
Value of the work
For the engineer: Practice readiness reviews, capacity reasoning, and cross-functional operational handoffs.
For the team: Produce a concrete launch-readiness assessment with measurable risks and recovery actions.
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.