[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

PENDING.md

@@ -4928,3 +4928,43 @@ Filed at `2af4335`, fixed at `37a2c86`, in that order. Every run below used a th
 **PENDING-182 ADDENDUM 2's recommended condition — PENDING-184 closed, D9 and D10 green — is met as of `37a2c86`.**
 
 **Awaiting:** CLOSED — `[FIX]` landed in `37a2c86`, steward-directed in session 2026-09-11.
+
+
+---
+
+## PENDING-185 — A state-claim falsifier whose unit is COARSER than the claim's, so the mechanism manufactures escalations
+**Date:** 2026-09-12
+**Tag:** [HARDENING]
+**Summary:** `claude-md-untouched-pending-150`'s falsifier is `file-changed-since d6377af CLAUDE.md`, whose unit is **the file**. The claim's unit is **a change made under PENDING-149**. The mechanism cannot express the claim, so it fires at `[ESCALATE]` grade on every future edit to `~/CLAUDE.md`, forever, 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 ran the other way, an instrument too fine or aimed at the wrong population. Those are correctable by reading more carefully. **This one is not correctable by reading at all.**
+
+### The instance
+
+The falsifier fired 2026-09-12 on `771bec6`. The substantive claim **holds**, established from the substrate rather than from any party's account of it:
+
+- `771bec6` is **+9/−2 on `CLAUDE.md` alone**; its three edits are the tag-is-a-claim block, Constraint 6's inbound-vocabulary sentence, and the fourth consequence under differently-biased checkers. None implements the buddy pattern; none touches §11.
+- **`CLAUDE.md` occurs zero times in PENDING-149's 8,806 characters.** Its **Files affected** are the buddy-pattern draft, the item, and PENDING-150.
+- PENDING-150 is open, `[ESCALATE]`, carries *"Files affected: `~/CLAUDE.md` (NOT edited)"* and *"Do not bundle with PENDING-149"*, and no `REVIEWED` entry is headed with it.
+
+⚠ **Provenance, stated because it bears on the weight of the confirmation:** the jurist proposed those edits, named itself the interested party, and invited the check in its own words — *"Do not take my word for the thing I did."* The confirmation above is from the diff and the item text, not from that account.
+
+### Why this is not a coarse check to be tightened
+
+A mechanism that manufactures escalations is worse than none. It is the shape REVIEWED-104 names in the other direction: *red on absent trains people to discount red*. A falsifier that fires truly, at the highest grade, on a claim it cannot evaluate will be dismissed by habit — and the dismissal habit is what a real firing would then have to survive.
+
+### Options
+
+- **(a) Narrow the unit.** Key the falsifier to something that can express *"under PENDING-149"* — a change touching the buddy-pattern draft or §11's text. ⚠ *"Under PENDING-149"* is authorship intent and **is not in the diff**; any content predicate over prose is the class that has failed repeatedly here (a word-guard passes on scrambled text).
+- **(b) Retire the falsifier; mark the state-claim manual-only.** Honest, and it is REVIEWED-104's third outcome applied to a falsifier: *could not be assessed* kept distinguishable rather than collapsed into a verdict.
+- **(c) Keep it and absorb a standing escalation on every `~/CLAUDE.md` edit.** Rejected on the paragraph above.
+
+**Recommendation: (b), recorded as a LOSS rather than presented as a fix.** It leaves the claim unwatched, which is what the state-claim mechanism existed to prevent. That cost should be visible in the register, not discovered later by whoever finds the claim unfalsifiable.
+
+### Cross-references, both ends
+
+Owner of the claim: `claude/governance/fool/seed/FOOL-SEED-RULE.md`, `<!-- STATE-CLAIM: claude-md-untouched-pending-150 -->`, placed under REVIEWED-127. Scope of the claim: **PENDING-149** (archived). Territory it guards: **PENDING-150**, open and unaffected.
+
+⚠ **NOT part of this item:** the textual collision in `~/CLAUDE.md`, where *"Four consequences bind"* now sits one clause from *"the three-party model is not a trust hierarchy"* while PENDING-150 is titled *a fourth position in the tripartite model*. Nothing was bundled; the collision is textual and will read as substantive to anyone searching for *fourth*. Annotating it **edits `~/CLAUDE.md`** and is therefore `[ESCALATE]`, the steward's hand. A jurist design-gate does not authorize it. Drafted and surfaced separately; **not written.**
+
+**Files affected:** `claude/governance/fool/seed/FOOL-SEED-RULE.md` (the STATE-CLAIM block); `scripts/governance-drift-check.py` if the unit changes; this item.
+
+**Awaiting:** Steward annotation. Placement design-gated by the jurist 2026-09-12 — new item rather than an amendment, on PENDING-145's suppression hazard.

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