Deliver
Build, integrate, and put the thing into service — with stop conditions and proof that matches the quality regime.
Before you write more code
Section titled “Before you write more code”If shape, language, framework, or placement is still hand-wavy, open Architecture first. Coding without those bets is rearranging smoke.
Implementation with stop conditions
Section titled “Implementation with stop conditions”- One deploy unit (or one package) with a done-when and owner — Work ownership.
- Prove as you go:
test-it, CI viarepos, readiness viacheck-readiness. - Refuse unearned complexity —
kiss.
Named ship plays (not synonyms)
Section titled “Named ship plays (not synonyms)”| Play | Means |
|---|---|
merge-it |
Land current work into the next integrate target (not automatically “production”) |
stage-it |
Land on staging |
ship-it |
Send all the way to production and check that it’s healthy |
Use the play that matches policy. Don’t call a merge a ship.
Open Architecture mid-delivery when…
Section titled “Open Architecture mid-delivery when…”- You’re about to add a second language, package, or host
- “Where does this concern live?” has no answer — What runs where
- Web UI vs docs stack isn’t chosen — Web framework selection