27 Bug-Hunt Stack – The Grimoire of Software Magic Words

28.1 Related Runes

1180 observability - Enough internal evidence exists that you can infer what the system is doing from the outside. Not logs alone: legible state under pressure.
1204 trace {Proof} - A preserved path through execution. Use it when the question is not only what failed, but where the causal thread first bent.
1172 invariant - A law that must remain true while the rest of the system is allowed to move. If you cannot say the invariant, you probably do not yet understand the change.
1562 regression - A previously solved bug or quality loss has returned.
1445 deterministic - Given the same inputs, the same result should return. This is the antidote to drift, heisenbugs, and unreviewable behavior.

Bug Diagnosis From Logs
Test Generation
Stack Grammar
Failure Modes
Canon Map | Step | Spell | Artifact | Advance when | | —- | ———– | ———————————- | ————————————————– | | 1 | Reproduce | Stable reproduction | The failure can be triggered on demand | | 2 | Localize | Smaller suspect surface | The search field is smaller | | 3 | Instrument | Logs, traces, asserts, or counters | New evidence can distinguish hypotheses | | 4 | Hypothesize | Likely failure mechanism | Repair surface is stated | | 5 | Patch | Minimal change | Patch matches current hypothesis | | 6 | Verify | Regression sweep | Defect is gone and neighboring behavior is checked |

{
  "steps": [
    2,
    3,
    4,
    5,
    6
  ],
  "until": "The bug is eliminated or evidence stops improving"
}

Escalate to a deeper diagnostic stack and preserve reproduction, traces, and rejected hypotheses.

It prevents patching before localization.