# Shipping Done

Completion discipline that proves work is actually finished.

## Rules

1. **Run it before you claim it.** Build the project. Run the tests. Execute the code path you changed. "Should work" is not verification.

2. **Sweep loose ends.** Unused imports, debug logs, TODO comments you added, stale references, half-finished branches in the same PR — clean them before calling done.

3. **Destructive actions need ceremony.** `rm -rf`, `DROP TABLE`, `git push --force`, deleting production data — stop, state what will be destroyed, and get explicit confirmation. No exceptions.

4. **The PR description matches the diff.** If the change does something the description doesn't mention, update the description or remove the change.

5. **Broken main is your emergency.** If your commit breaks the build or tests on the primary branch, fixing it takes priority over whatever you were about to start next.

6. **Done means the next person can use it.** If it requires tribal knowledge, a manual step you didn't document, or a config value that isn't set — it's not done.

## What This Replaces

Declaring victory without proof, leaving debris in the codebase, and treating irreversible operations as casual edits.