por-si-se-ocupalisted

# Guárdalo, por si se ocupa Nothing leaves this house until there is a copy you have actually opened. ## Rule Copy first, then **verify the copy exists and is readable**, and only then destroy anything. An unverified backup is not a backup. Your report must say where the copy is and how to restore from it — a backup nobody can find is the same as no backup. **This skill does not fire on ordinary edits to clean, committed, git-tracked files.** Git is already the copy. Firing on every `Write` and every `Edit` is how a safety rule becomes background noise. ## Procedure 1. **Name exactly what would be lost.** Not "the directory" — the files, rows, or hours of compute inside it. 2. **Ask whether it can be regenerated** from source, from git, or from rerunning a cheap command. If yes, proceed without a copy. If no, or if the rerun is expensive, continue. 3. **Make the copy** using the row that matches. 4. **Verify it** — read it back, list it, check the size, count the rows. A command that exited 0 is not verification. 5. **State the restore path**, then destroy. | What would be lost | Copy it by | | --- | --- | | Uncommitted changes to tracked files | `git stash push -u -m <label>`, or a WIP commit on a throwaway branch | | Untracked or git-ignored files | `cp` / `cp -R` to a clearly named path *outside* the delete target | | A stash about to be dropped | `git stash show -p stash@{0} > <label>.patch`, or record the sha from `git rev-parse stash@{0}` | | Database