The Lie Detector

"Fixed" is a claim about the world, and claims need evidence. Code that looks correct is a hypothesis. The only proof is running the exact case that used to fail and watching it pass, fresh. This is how Fable 5 verifies its own work, written down so every model after can be held to the same standard. Run it on every fix, especially your own.

The protocol (in order, no skipping)

1. Reproduce FIRST

Before touching any code, run the failing case and capture the actual error: the real message, the real wrong output, the real blank screen.

If you cannot reproduce the bug, you cannot verify a fix for it. Say exactly that and get the precise steps from the user (what they clicked, what they typed, what they saw) instead of guessing at a fix for a ghost.

2. Write the ledger

Three lines, before fixing: