Task library BREADINESS Site reliability · Phased project Seasonal traffic readiness review A fictional course platform expects a registration deadline spike. Capacity assumptions, escalation ownership, and degradation decisions are scattered across old documents.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 26h 30m + setup
Suggested stack TypeScript · PostgreSQL · HTTP Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with BREADINESS-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice readiness reviews, capacity reasoning, and cross-functional operational handoffs.
What the team gains Produce a concrete launch-readiness assessment with measurable risks and recovery actions.
Before you start Create synthetic registration traces and local dependency doubles with finite connection and request limits. Delivery agreement Deliver a local rehearsal and review packet; external launch approval remains outside the exercise.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Define demand, dependencies, and launch invariants.
PHASE 2 Exercise saturation and failure paths.
PHASE 3 Make readiness gaps and controls reviewable.
Collect assumptions Define demand, dependencies, and launch invariants.
BREADINESS-101 Entry ticket; project setup still required Estimated field mix
Performance engineering 60% Site reliability 40% BREADINESS-102 Depends on BREADINESS-101 Estimated field mix
Site reliability 60% System design 40% Test constraints Exercise saturation and failure paths.
BREADINESS-103 Depends on BREADINESS-102 Estimated field mix
Database engineering 40% Site reliability 40% Performance engineering 20% BREADINESS-104 Depends on BREADINESS-101 Estimated field mix
Backend 40% Quality engineering 30% Distributed systems 30% BREADINESS-105 Depends on BREADINESS-104 Estimated field mix
Distributed systems 40% Backend 40% Site reliability 20% BREADINESS-106 Depends on BREADINESS-103, BREADINESS-105 Estimated field mix
Site reliability 60% Backend 40% BREADINESS-107 Depends on BREADINESS-103, BREADINESS-106 Estimated field mix
Performance engineering 50% Distributed systems 30% Site reliability 20% Prepare operations Make readiness gaps and controls reviewable.
BREADINESS-108 Depends on BREADINESS-102, BREADINESS-107 Estimated field mix
Performance engineering 40% Site reliability 40% Cloud infrastructure 20% BREADINESS-109 Depends on BREADINESS-108 BREADINESS-110 Depends on BREADINESS-109 Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.