diff --git a/claude/memory/MEMORY.md b/claude/memory/MEMORY.md
index 5f60891..34b7412 100644
--- a/claude/memory/MEMORY.md
+++ b/claude/memory/MEMORY.md
@@ -56,7 +56,7 @@ permalink: claude-memory/memory
 ## Canonical Workstream Trackers
 *Read the tracker for any active workstream at /wake-up before composing the briefing. Append substantive moves at /wrap-up — to the **chronological log**, not only "current state". Per `feedback-canonical-workstream-tracker-discipline.md`.*
 - **[Chamber as versioned releases](project-chamber-versioned-releases.md) — THE GOVERNING FRAME for all library work.** The 2000-year Chamber as versioned releases with soft borders, each serving a PURPOSE; scope every library bite through this. **Open decision: which purpose anchors V1.** Read the file, not this line — it holds the reframe that resolved the purpose/scope paralysis.
-- [Studium Engine](project-studium-engine.md) — canonical engine tracker; **read it, this line holds no state.** **fr cell: ONE STEP DONE, THE SECOND BLOCKED** (measured 2026-09-05, was "two steps from closing"). PENDING-134's disclosure is PLACED (`9221dd8`). ⚠ **CORRECTED 2026-09-05, same day: the pass HAD ALREADY RUN** — `docs/fr-reported-speech-identification-pass-2026-08-13.md`, commit `de1c34b`, authorized by REVIEWED-116 pt 5 as an identification pass that **writes nothing**. I read the absence of F4 markers as the absence of the act; a no-write pass leaves exactly that trace. Its finding: reported speech in **one** grounded span (L1551), reclassified out the same day (REVIEWED-119) — so within the grounded set P7's F4 tagging was **correct and complete**. Re-read independently 2026-09-05 across the enumerated **8**: zero reported speech, result reproduced. ✅ **THE fr CELL IS CLOSED — 2026-09-06, steward act (`346d8e8`). THE ONE-SHOT RATIO IS SPENT; DO NOT DERIVE AGAIN.** Bare `ratio_A_to_B` **RETIRED** — two populations disagree and the instance figure **1:9 equals the retired VOID figure under a DIFFERENT population** (writing it would have read as confirming the old number). Now `..._grounded_spans: "1:7"` (the historical population, REVIEWED-118 pt 3) and `..._grounded_instances: "1:9"`. ⚠ **Against §6.2's A:B ≈ 1:1 the inherited fr gold DOES NOT MEET THE RULE — and what follows is NOT decided.** ⚠ **CLOSED ≠ SETTLED:** doctrine never fired · defeater never able to fire · 73-span citation-safety exposure untouched · single-reader condition stands. The cell entry carries the full open list — read it, not this line.
+- [Studium Engine](project-studium-engine.md) — canonical engine tracker; **read it, this line holds no state.** ✅ **fr cell CLOSED 2026-09-06** (steward act, `346d8e8`) — **the one-shot ratio is SPENT; DO NOT DERIVE AGAIN.** Bare `ratio_A_to_B` retired; `..._grounded_spans: "1:7"` is the historical population, `..._grounded_instances: "1:9"` **equals the retired VOID figure under a DIFFERENT population** — the trap. ⚠ **Against §6.2's A:B ≈ 1:1 the inherited fr gold DOES NOT MEET THE RULE; what follows is NOT decided.** ⚠⚠ **CARRIED HERE BECAUSE A QUALIFIER INSIDE A CLOSED ENTRY IS READ AS HISTORICAL: every "verified by reading" claim in the fr cell rests on ONE READER** (REVIEWED-121 pt 8) — the pass, its 2026-09-05 replication, and the ratio enumerations. **The replication does NOT discharge it: same party, twice.** It lifts when a second reader reads, and not before. ⚠ CLOSED ≠ SETTLED — doctrine never fired · defeater never able to fire · 73-span citation-safety exposure untouched; the cell entry carries the full open list.
 - [Studium engine telos — the chamber of voices](project-studium-engine-telos-chamber-of-voices.md) — **the ultimate goal, above the build plan**: the childhood chamber of hero-voices, rebuilt so the counsel is *accountably* theirs. Why verbatim fidelity is load-bearing.
 - [The Chamber touchstone — the *why*](~/_Dev/studium-engine/docs/the-chamber-touchstone.md) — seven questions to test work against when lost in the trees. **Read at Step 0 of any chamber work.** Holds no state; does not decay.
 - [The Chamber vision is NOT in one place](project-chamber-vision-is-not-in-one-place.md) — it lives in **seven** sources across two repos + memory. A single home would become an eighth unless it supersedes or points.
diff --git a/claude/memory/knowledge-graph.jsonl b/claude/memory/knowledge-graph.jsonl
index ca36c23..56e90db 100644
--- a/claude/memory/knowledge-graph.jsonl
+++ b/claude/memory/knowledge-graph.jsonl
@@ -794,3 +794,5 @@
 {"subject": "the-open-authorization-queue", "predicate": "has-no-cardinality", "object": "114 unclosed headers / 64 after the closure filter / 56 once two readers stop miscounting / 43 once four rows are seen as two items. All defensible. The 64 carried for weeks was an artefact of which reader was asked. 54 after the 2026-09-06 corrections, and it is a MAINTAINED number.", "valid_from": "2026-09-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-06-the-count-had-no-referent.md", "extracted_at": "2026-09-06"}
 {"subject": "pending-134-whose-proposition-doctrine", "predicate": "governs", "object": "zero spans; has never fired. Both F4 spans left the grounded set by independent routes (L926 retracted REVIEWED-118, L1551 reclassified REVIEWED-119) before it could reach them.", "valid_from": "2026-09-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-06-the-count-had-no-referent.md", "extracted_at": "2026-09-06"}
 {"subject": "claude-code", "predicate": "drift-pattern-good-direction", "object": "wrote the negative control against the FAILURE MODE rather than the observation — 'does NOT yield the bare family name'. A wrong ident and an unseen header fail identically downstream, so a control checking only 'was it seen' would have passed throughout the bug's life.", "valid_from": "2026-09-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-06-the-count-had-no-referent.md", "extracted_at": "2026-09-06"}
+{"subject": "the-conceals-live-asks-floor-rule", "predicate": "arrived-by-correction", "object": "NOT the jurist's good judgement. Its rule as first stated (does this block Chamber, ARC or L1) would have deferred PENDING-145/-146 as queue mechanics WHILE THEY CONCEALED FOUR LIVE ASKS. The instance forced the amendment; the rule was wrong and got caught. Recorded this way because a rule arriving by correction should carry the correction with it.", "valid_from": "2026-09-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-06-the-count-had-no-referent.md", "extracted_at": "2026-09-06"}
+{"subject": "single-reader-condition-fr-cell", "predicate": "survives-closure", "object": "Carried in MEMORY.md, not only in the now-closed cell entry: a standing evidentiary qualifier inside a closed record is read as historical. The 2026-09-05 replication does NOT discharge it — same party, twice. Lifts when a second reader reads.", "valid_from": "2026-09-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-06-the-count-had-no-referent.md", "extracted_at": "2026-09-06"}
diff --git a/claude/memory/session-2026-09-06-the-count-had-no-referent.md b/claude/memory/session-2026-09-06-the-count-had-no-referent.md
index bd1285a..1f3f0e4 100644
--- a/claude/memory/session-2026-09-06-the-count-had-no-referent.md
+++ b/claude/memory/session-2026-09-06-the-count-had-no-referent.md
@@ -128,7 +128,10 @@ Not because it is urgent; because it is the only thing that determines whether t
 a maintained number, not a fact.** It will drift the way 64 did. The jurist's proposed rule (*does
 this block Chamber, ARC or L1*) versus the executor's (*would a ruling produce an act someone would
 actually take*) is worth **43 items versus 20** — stated as a number for the first time. And the
-jurist amended its own rule mid-session, earned by instance:
+⚠ **the jurist's rule was WRONG and got caught** — not amended by good judgement.
+Its own account, recorded that way because a rule arriving by correction should carry the
+correction with it: as first stated it would have deferred PENDING-145/-146 as queue mechanics
+**while they were concealing four live asks**. The instance forced it:
 
 > **An instrument fault that CONCEALS LIVE ASKS is blocking, whatever it is about. You cannot triage
 > what you cannot see.**
@@ -172,8 +175,12 @@ no rule set, that is the session's actual failure and it will not look like one.
 
 **Not** *"am I being careful about stale claims?"* — self-report, unfalsifiable from inside.
 
-> **Did the banked rule fire on a record I was not already suspicious of?** The record answers it:
-> `feedback-a-dated-measurement-is-not-a-status` was banked 2026-09-05 and fired the next day on
-> `studium-engine/CLAUDE.md` — a surface nobody was auditing, caught only because the rule made me
-> look. **Does it fire a third time, on something I did not write?** If it only ever catches my own
-> recent output, it is a proofreading habit and not a rule.
+> **Did the banked rule fire on a record I was not already suspicious of?** Banked 2026-09-05, it
+> fired the next day on `studium-engine/CLAUDE.md` — a surface nobody was auditing. **Does it fire a
+> third time, on something I did not write?**
+>
+> ⚠ **TWO failure conditions, and the second will look like success.** (i) It never fires on foreign
+> material. (ii) **It fires, but on material recent enough that ordinary attention would have caught
+> it anyway** — which reads as a hit and is not one. *If the third instance is another surface
+> touched in the same session, that is still the proofreading habit.* The passing case is a record
+> **neither written nor touched by the session that catches it.**