[HARDENING] PENDING-185: a state-claim falsifier whose unit is coarser than the claim's

The falsifier `file-changed-since d6377af CLAUDE.md` fired on 771bec6. The claim it
guards — that ~/CLAUDE.md has not been touched under PENDING-149 — still HOLDS.

Established from the substrate, not from the account of the party that proposed the
edits and named itself interested: 771bec6 is +9/-2 on CLAUDE.md alone and carries the
three Anthropic threat-report edits; `CLAUDE.md` occurs zero times in PENDING-149's
8,806 characters, whose Files affected are the buddy-pattern draft, the item, and
PENDING-150.

The defect is the mechanism's unit. The falsifier's unit is THE FILE; the claim's unit
is A CHANGE MADE UNDER PENDING-149. It cannot express the difference, so it fires at
[ESCALATE] grade on every future edit to ~/CLAUDE.md, indefinitely, each firing needing
a human read to dismiss. Third granularity instance this week and the first with the
instrument coarser than the claim — the other two are correctable by reading more
carefully; this one is not correctable by reading at all.

Recommendation is (b), retire and mark manual-only, recorded as a LOSS rather than
presented as a fix: it leaves the claim unwatched, which is what the mechanism existed
to prevent.

FOOL-SEED-RULE.md carries the second end of the cross-reference, placed after the
STATE-CLAIM marker so the parser is untouched, and logged in that document's own §7
post-beacon audit trail as it requires. The stale §6 bullet is deliberately NOT struck:
it is pre-registration record and its worth is being what was claimed before the beacon.

NOT included, and escalated instead: the one-line annotation in ~/CLAUDE.md for the
"Four consequences bind" / "fourth position" textual collision. That edits the
constitution and is the steward's hand; a jurist design-gate does not authorize one.

Placement design-gated by the jurist (new item, not an amendment, on PENDING-145's
suppression hazard). That reasoning stands independently and is retained.

Verified: heading parses at col 0, no indented variant, two negative controls at 0,
prefix preserved, drift check 65/65, STATE-CLAIM marker byte-intact across all 5 lines.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PJM5fwqp456LDGzqiZXsgu

claude/governance/fool/seed/FOOL-SEED-RULE.md

@@ -309,6 +309,26 @@ which is the entire point of having filed it early. Current state lives in
 *(The first negative state-claim in this system to carry a falsifier. It is the one bullet
 in §6 still true, it is `[ESCALATE]`-grade the moment it stops being true, and until today
 nothing in this system would have noticed. REVIEWED-127.)*
+
+⚠ **THE FALSIFIER FIRED 2026-09-12, AND THE CLAIM IT GUARDS STILL HOLDS.** `771bec6` edited
+`~/CLAUDE.md`, so `file-changed-since` fired as designed. Those edits are the three derived
+from the Anthropic threat report; none is made under PENDING-149, whose **Files affected**
+are the buddy-pattern draft, the item, and PENDING-150 — `CLAUDE.md` appears nowhere in its
+8,806 characters. Established from the diff and the item's own text, **not** from the
+account of the party that proposed the edits, which named itself interested and asked that
+its word not be taken.
+
+**The falsifier's unit is the FILE. The claim's unit is a change made UNDER PENDING-149.**
+The mechanism cannot express the difference, so it will fire on every future edit to
+`~/CLAUDE.md`, at `[ESCALATE]` grade, indefinitely. **Do not read a later firing as evidence
+that this claim has broken.** PENDING-185 carries the remedy and awaits the steward;
+PENDING-150 remains open, `[ESCALATE]`, and unaffected.
+
+The §6 bullet above and the STATE-CLAIM block are **deliberately left unaltered.** The
+bullet's plain reading is now stale — `~/CLAUDE.md` *has* been touched, just not under
+PENDING-149 — but it is pre-registration record, and its worth is being what was claimed
+before the beacon. Correcting it here rather than rewriting it there is the whole reason
+this section is preserved verbatim-struck elsewhere.
 - Nothing has been implemented of §8, §8a or §9 — the status line is confirmed free but
   not built.
 
@@ -324,6 +344,7 @@ stays auditable instead of eroding one silent correction at a time.
 |---|---|---|---|
 | 2026-08-25 | `abandonment` → `retirement`: §4's alias and naming note, §5b marked done | jurist ruling recorded in §5b, which itself scheduled the change *after* the beacon | **no** — the word naming a criterion, never the criterion |
 | 2026-08-25 | §6 marked superseded in part | Constraint 4, honest degradation | **no** — §6 is a status claim, not a rule |
+| 2026-09-12 | §6 — a ⚠ note added *after* the STATE-CLAIM marker recording that the falsifier fired, that the claim still holds, and that the mechanism's unit is coarser than the claim's. The §6 bullet and the marker block itself are untouched. | Constraint 4, honest degradation; PENDING-185 filed the same day, placement design-gated by the jurist | **no** — §6 is a status claim, not a rule; and the edit is prose adjacent to the marker, not the marker |
 
 ⚠ **Nothing in §1, §2, §2a, §3, §5 or §5a has been edited.** Those are the clauses that
 governed the derivation, and they stand exactly as they stood when it ran. This is not an