Shipping Changes

It walks you through research, writing a proposal doc, implementing in reversible phases, and self-reviewing your PR before merge. The core discipline is the guarded commit chain: assertions, tests, and verification all have to pass before anything gets committed, using shell && short-circuiting so a single failure blocks the commit entirely. It includes impact analysis checks if you have abyss available, and pushes you to honestly flag known tradeoffs in your self-review rather than hiding them. Use it when a change is big enough to warrant a written plan, or when you want to ship risky work in rollback-friendly stages. For small, low-risk edits, skip the ceremony and just ship.