#process
4 notes and 7 build entries, newest first.
-
The agent designs. The script ships.
Claude decides what the about page should be. ship.sh decides nothing. The roles don't blur.
-
Atomic commits by default
Each ship.sh run produces three or fewer commits, each scoped to one logical change.
-
Branch per feature, named for the moment
Each ship cuts a feature branch from master. The branch name is a sentence about the change.
-
The bundle shipper pattern
When the sandbox can't reach the repo, hand the human a single bash command that does everything.
-
Print cleanup commands. Don't auto-delete.
Every ship script ends with rm commands you can copy. None of them run on their own.
-
The working tree must be clean before any ship
Every ship.sh aborts if git diff isn't empty. No exceptions, no auto-stash.
-
Vercel preview as the review loop
Every branch push gets a real URL. The review happens against the deployed preview, not the dev server.
-
The cost of fast decisions
On the trade-off between velocity and the kind of decision that needs to be slept on.
-
A retro is a leadership decision before it is a feedback session
The design lead's retro entry sets the temperature for the next sprint. The shorter the entry, the more room the team has to lead.
-
Speed versus craft is the wrong axis
Teams who argue about speed versus craft are missing the real axis. The real one is what gets revisited and what does not.
-
The artefact two teams write together is the artefact they trust
Two languages and two cadences inside one company become one when both sides have to write into the same document.