pasteurizelisted

# /pasteurize Use this process for hard bugs. ## Discipline **Iron Law:** Build a reliable feedback loop before you form one hypothesis. Stop at each red flag: - You name a cause before the loop reproduces the failure. - You accept an unrelated failure as the reproduction. - You add a test at a mocked seam because the real seam is difficult. - You make a fourth fix attempt on the same hypothesis list. - You report a clean worktree without the session-tag sweep. | Rationalization | Answer | | --- | --- | | "The cause is obvious." | Build the loop. An obvious cause takes one run to confirm. | | "The loop is too slow to write." | A slow loop still beats a wrong fix. | | "Any failure proves the bug." | Match the expected exit code or output. | | "The mocked seam is close enough." | Record the missing seam and route to Mold. | | "One more attempt will work." | Write a new hypothesis list first. | Follow [`code-intelligence-routing.md`](../cheese/references/code-intelligence-routing.md) when you explore code. Resolve the specification store with `artifact-path specs`. Read the notes about the failed seam from the resolved directory. Read [`harness-portability.md`](../cheese/references/harness-portability.md) for portable tool use. Use bundled or repository helpers before `${CLAUDE_SKILL_DIR}`. Treat `${CLAUDE_SKILL_DIR}` as an optional host fallback. Use the handoff blocks as the portable contract. Remember that slash commands are host renderings, not the control model. ##