InsanelyGreat

New in v2.14

You can now let the agent run the loop. It still can’t ship.

The orchestrator has always proposed and waited. The autonomy ladder adds two opt-in rungs above that: advance, where bare /ssd executes its own unambiguous next step — one phase per invocation, never more — and /ssd run <slug>, which walks design → code → review → gate unattended, looping coder and reviewer until the gate passes or a budget stops it. The default is unchanged: with no autonomy block configured, the orchestrator makes no additional call at all.

What it cannot do is the actual design. ship, deploy, rollout-advance and flag-removal are refusals with no bypass flag — because a feature is bounded by two irreducibly human decisions, the brief at the start and the ship at the end. Autonomy delegates the middle and neither end. Every transition is announced, written to disk, and only then executed, so a run that dies mid-flight is recoverable rather than mysterious. And the run records the gate script’s exit status rather than its own opinion of how it went.

Also new: rail deviations are finally real. The rails promised since v1.15 that every skipped step gets recorded; measured across 15 workstreams, nothing had ever written one. A writer and a gate rule that reads it back now ship together — and an auto-run records zero of them, by construction.