git-safety-net

1# Git Safety Net
2 
3Prevent losing work in a tangle of branches/stashes/rebases, and recover it forensically
4when something already went sideways. The commands here are all **non-destructive or additive**
5until a step is explicitly labeled destructive — recovery must never make the loss worse.
6 
7## Outcome contract — keep the safety net subordinate to the user's job
8 
9Before Mode B/E or any command that writes a ref or backup, state the following in the conversation
10(do not create another file):
11 
12- **Outcome:** the user-visible end state, in the user's words.
13- **Current phase:** what is authorized now. "Later" work is not authorized in this phase.
14- **Authorized targets:** named objects this phase may inspect, plus the subset it may change.
15- **Stop condition:** observable facts that end the task.
16 
17Then enforce these boundaries:
18 
19- **Evidence scope is not action scope.** A read-only audit may discover another clone, ref,
20   repository, or dangling object. That discovery may widen the report; it does not authorize
21   preserving, uploading, merging, deleting, or otherwise changing the newly found object.
22- **Authorization is object-specific, not repository-wide by implication.** "Take over",
23   "continue", or "finish the cleanup" applies only to the checkout/ref/PR the user identified.
24   A collaborator-owned worktree, branch, or PR discovered later stays report-only until the user
25   names it as a change target. If the user says to leave it alone, record that exclusion and do
26…