Required deliverables
What you must ship
- test pyramid for TaskFlow
- security threat model
- structured logs/correlation IDs
- performance baseline + improvement
Mastery milestones · Phases 28–31
Production Engineering
Prove behavior, harden trust boundaries, diagnose incidents, and optimize with measurements.
Constraints
Rules that make the project meaningful
- At least one authorization regression has an automated test.
- Sensitive data is excluded from logs.
- Performance work includes before/after evidence.
Execution sequence
Build without following a transcript
- 01
Write acceptance criteria and a boundary diagram before implementation.
- 02
Create a clean checkpoint/branch and inventory the existing files, routes, database objects, and configuration you are allowed to change.
- 03
Build one vertical slice that reaches an observable result end-to-end before broadening the feature.
- 04
Add the remaining required behavior incrementally. After each coherent change, run the narrowest verification and inspect the output.
- 05
Exercise at least two non-happy paths: malformed/missing input, authorization failure, network/database failure, race condition, or configuration error as applicable.
- 06
Run the full milestone quality gate and record results.
- 07
Perform a closed-reference rebuild or architecture walkthrough. Document trade-offs and one deliberate non-goal.
Evidence packet
Prove that the milestone works
01
Repository/file-tree diff
02
commands and exit status
03
browser/API/database evidence
04
one controlled failure + diagnosis
05
tests/quality-gate result
06
short architecture decision note
Review rubric
What good looks like
Correctness
Required behavior works and failure paths are deliberate.
Architecture
Responsibilities and dependency direction match the course model.
Evidence
Claims are backed by repeatable commands, requests, tests, or stored data.
Debugging
At least one failure is reproduced, isolated, fixed, and reverified.
Independence
The final feature can be explained or partly rebuilt without copying the reference.
Milestone progress
Mark complete only after the evidence packet
A milestone is complete when the deliverables, failure testing, and review rubric are satisfied without following a transcript.