/pasteurize

A discipline for hard bugs. Skip phases only when explicitly justified.

When exploring the codebase, use /cheez-search to orient and check .cheese/specs/ for any spec or design notes that touch the failing seam.

Phase 1 — Build a feedback loop

This is the skill. Everything else is mechanical. If you have a fast, deterministic, agent-runnable pass/fail signal for the bug, you will find the cause — bisection, hypothesis-testing, and instrumentation all just consume that signal. If you don't have one, no amount of staring at code will save you.

Spend disproportionate effort here. Be aggressive. Be creative. Refuse to give up.

Ways to construct one — try them in roughly this order