Your finding becomes a rule the harness checks the same way every time.
Claude Code. You give a finding from Tuesday's outage: migration 0042 ran CREATE INDEX on payments without CONCURRENTLY, and writes to payments blocked for 9 minutes. You ask for a rule for the team that covers every table, except a table created in the same migration. With moo off, a dialog asks whether migration 0043, which has the same bug, has run in production, and you pick not yet. Claude writes the rule in the README, enforces it with a test that runs squawk, a migration linter it installs from npm, rewrites 0043, adds an install step to CI, and reports 5 of 5 tests passing. With moo on, you type /hope:anchor and the same words. No dialog opens. The reply states the rule in one sentence, then as an if/else check, then as a table of cases: 0042 and 0043 rejected, 0042 rewritten passes, an index on a partitioned table marked as a gap. It shows 0042 rewritten, says it doesn't know whether production has run 0043, and asks whether fixing 0043 and a test that enforces the rule should come next.