Triage Index
About to run something wide, destructive, or public? Part III first.
That is the one line on this page to memorize. Everything else here is lookup.
There are two tables, and they are keyed on your posture, not on the book's parts: chapters from every part appear in both. If your hand is on the command, use the first. If you are staring at a screen you do not believe, use the second.
Before you act
| You are about to | Go to |
|---|---|
| Run one command against many targets. A sweep, a bulk commit, a find-and-replace, anything where the word all, or a wildcard, decides what gets touched. | 9. The Multiplied Mistake |
| Run something that destroys state or releases state. Force, drop, remove, delete a worktree or a stash, or push anything public for the first time. | 10. One-Way Doors |
| Add a gate, a checklist, a confirmation step, or a second review, and you are wondering what it will cost every day after today. | 11. The Discipline Budget |
| Spend an unrepeatable run on an instrument you have never fed a known answer. | 4. The Lying Instrument |
| Write into a shared space, and you have not checked who else is in it. | 5. The Crowded Tree |
Wide and irreversible at once is chapters 9 and 10 both, and the two nest: name the full list first (chapter 9's first step), enumerate what is behind every item on it (chapter 10), and pilot only on what survives. Where they meet at the door, the door outranks the count.
Something already happened
Find the row that matches what is on your screen. Route on what you can see, not on what you suspect is behind it.
| What you can see | Go to |
|---|---|
| It says done and you don't believe it. The check is green, the exit code is zero, the message says merged, and you cannot point to the thing the success was supposed to produce. | 1. The False Green |
| It says failed, and you suspect the failure itself. | 1. The False Green |
| You changed it and nothing changed. No error, no warning, no rejected write, and the behavior is exactly what it was before you touched it. | 3. The Unwired Switch |
| You are executing something written before now, a checklist, a handoff, a doc, your own notes, and the world does not match it. A step is already done, a file it names does not exist, the documented command fails. | 2. The Stale Record |
| You are about to claim something is missing, or to build something you cannot quite believe does not already exist, and the record you are reasoning from has not been refreshed. | 2. The Stale Record |
| A comment in the file tells you not to make the change you are about to make, and you are deciding whether it still counts. | 2. The Stale Record |
| A number is asking you to act on it, and the number is off. Clean, specific, machine-produced, and you do not believe it. | 4. The Lying Instrument |
| Something moved and you did not move it. Bytes on disk changed under you, a branch switched, a file appeared, a lock is held, and every process you can name denies it. | 5. The Crowded Tree |
| A worker you dispatched says the work is done, and you cannot find the work. The report is better than the diff. | 6. The Confident Delegate |
| It passed on your machine and failed on theirs. Or a check failed before your code could possibly have run. | 7. Not Your Machine |
| A control you installed just refused you, and you are sure it is wrong. Your hand is moving toward one more exclusion, one looser pattern, just for today. | 8. The Guard You Argue With |
| You are halfway through a batch, the outputs scrolling past uniform and green, and the uniformity itself has started to bother you. Or a batch reported clean and one item turns out to have been nothing like the others. | 9. The Multiplied Mistake |
| The door already closed. Something was deleted, or published, and cannot be walked back. | 10. One-Way Doors |
| Nothing is failing and the work is still not moving. Every routine operation arrives at your elbow as a request for permission, or a whole session went to process and no artifact came out. | 11. The Discipline Budget |
If two rows fit
Chapters 9 and 10 are settled above, at the door. Four questions settle the rest.
Was the claim ever a fact? A signal that was born false is chapter 1. A record that was true the day it was written and describes nothing today is chapter 2. If no claim is involved at all, only your own write with no effect, that is chapter 3.
Who produced the thing you distrust? The system reporting on itself: chapter 1. A tool you pointed at the system: chapter 4. A worker you dispatched: chapter 6. A peer you never dispatched and that owes you nothing: chapter 5.
Are there two environments in the story? If the same bytes genuinely behave two ways in two places, chapter 7. If everything happened on one machine and the green simply did not mean success, chapter 1.
Whose gate said no? Yours: chapter 8. A platform's, a registry's, a provider's: chapter 7. Nothing fired, and the friction is an untested assumption of your own: chapter 11.
Every chapter opens with a section called You are here if, and closes with the doors into its neighbors. A wrong row costs you one page: the chapter's first paragraphs will name the right one and send you there.
And if no row fits at all, do not pick a chapter by analogy. Write down the signal you can actually see and treat the failure class as not established; the preface says which kinds of lesson this book refuses, and the afterword names the one class it could never stock.