anchor · diff
git:20260817.0cc07d9 to git:20260817.f04083f
4 added, 31 removed. Audit A to A.
---
name: anchor
description: Rewrite a rule so anyone applies it the same way. Use when a stated rule or claim takes the reader's judgment to apply.
---
- ## Extract
-
- From the conversation/context/user:
-
- - The **rule** as stated
- - Its **grounds** — the cases it came from, where it fires, what it decided.
-
- ## Gate
-
- Proceed only when: A rule is already stated and the complaint is checkability "two readers could disagree where it fires".
-
- Anything else, say which in one plain line and stop — never anchor anyway:
-
- - Nothing stated yet → there is no rule to anchor.
- - The complaint is coverage, not checkability → use **widen** skill.
- - The cases changed, or the rule now serves a different objective → stop, the rule needs deriving fresh, not anchoring.
-
- ## Loop
-
- 1. Find where the judgment hides: the word or clause two readers would apply differently.
- 2. Replace it with something mechanical:
- - a question with a yes/no answer
- - a check a machine could run
- - a fixture with win conditions anyone reads off the same way.
-
- Prefer the trigger a machine could evaluate over the one a careful reader could.
+ Find where the judgment hides: the word or clause two readers would apply differently. Replace it with something mechanical — a question with a yes/no answer, a check a machine could run, a fixture with win conditions anyone reads off the same way. Prefer the trigger a machine could evaluate over the one a careful reader could.
- 3. Silently AUDIT the rewritten rule:
- it must decide every case the original decided, the same way.
- Each case it loses means you narrowed — back off by the minimum until every case fits again.
+ Silently audit the rewrite: it must decide every case the original decided, the same way. Each case it loses means you narrowed — back off by the minimum until every case fits again.
- ## Output
+ Hand back the rule with its mechanical trigger, and show it deciding one of the cases it came from so the user watches it run. Name any judgment that resisted going mechanical — that part is still open.
- Hand back the rule with its mechanical trigger, and show it deciding one case from the grounds so the user watches it run.
+ The complaint is coverage, not checkability → use **widen** skill. The cases changed, or the rule now serves a different objective → the rule needs deriving fresh, not anchoring.