Cheat notes · Module 07 · Prove it
Capstone: the first decision and the first 90 days
A five-minute review for when you have done this module and want it back in your head. Open the full module for the steps and the lab, or the full text to print.
The idea
An ADR keeps the context, options and consequences of a decision next to the design; the 90-day plan turns it into three phases that each end on a measured result.
Remember
- ADR sections after Nygard (2011): title, context, decision, status, consequences; this course adds options considered (
D2,D3). - An ADR is never rewritten: a new one supersedes it.
- Phases: see it (0-30), pave it (31-60), prove it (61-90) (
N1). - Each phase
exitnames a scorecard metric and a result (N3). - CNCF maturity levels: provisional, operationalized, scalable, optimizing.
Pitfalls
- An exit on a date fails
N3: time passing proves nothing. - An ADR with one option was not a decision (
D3). - Editing an old ADR loses why the old decision was right then.
Commands
git switch -c adr-0002 | A branch for the change |
gh pr create --fill | Open a pull request |
gh pr checks --watch | Wait for the design check |
gh pr merge --squash --delete-branch | Merge it |
Test yourself
Answer in your head first, then open the answer.
Why list options in an ADR?
So a later reader sees what was weighed and can tell if the decision still holds.
What do you do with an ADR that no longer fits?
Write a new one that supersedes it and mark the old one superseded.
Where does the plan keep the dates?
In each phase's days; the exit keeps the result.
Where module 07 leaves you: docs/adr/0001-first-golden-path.md and plan/90-days.yaml pass the check. Your own docs/adr/0002-*.md is merged through a pull request with a green check. Every part of the design passes npm run check.