The Software Factory — Proof Before Commit
Release Slices and the Ship Gate
Ship the Smallest Useful Thing First
/todo tags every story core or later:
- the core slice is the smallest set someone can use once it ships — the engine, the screens or commands that expose it, and the flags, routes, migrations and runbook it needs
- saved state, measurement, admin tooling and polish are later unless the core is unusable without them
- the core slice ships on its own: no core story depends on a later story, and no wave mixes the two
release-slice.js reports where a run stands: core, ship-gate, later (only with --later-approved) or complete.
The Ship Gate
A TODO with a later slice has a Ship gate. When the core slice is done, /run-todo runs:
- a final review of the core slice, logged as
Review — final (core) - a release packet in the plan's
## Ship Gatesection: the core stories and commits, flags, migrations, a runbook with its rollback target, the evidence and the open items - the owner's decision, recorded verbatim:
**Later slice go:** {date} — {owner's words}
The go can be given up front, in the run's one round of owner questions. When it is already recorded and no new outward action has come up, the run writes the packet and continues into the later slice without a fresh stop. Otherwise it stops and asks: ship the core and continue, stop here, or re-plan. With no go, a headless run (--no-ask) ends needs-human at the gate.
What the Go Covers
The later-slice go covers building the later slice. It does not cover pushing, deploying, publishing or a fleet sync — each of those still needs its own explicit go.
The Ship gate is a decision point, not a formality. In the worked example the owner said yes to building the later slice before the run started, and "not yet" to pushing the core — two separate answers, both recorded.
The owner gives the go for the later slice. What may the run now do?