session 2026-08-06: Constraint #1 wording (steward-enacted) + PENDING-106/107 corrections + PENDING-89 docket; BMF stopped and disabled; chavruta retrieval measured

claude/memory/knowledge-graph.jsonl

@@ -572,3 +572,10 @@
 {"subject": "the positive-control-before-any-absence-claim rule", "predicate": "prevention", "object": "Caught a failure class it was not written for. The rule was written for GATE-absence claims ('do not report no gate found without showing the method detects a gate elsewhere'). What it actually caught was a TOOLING artifact: zsh glob-expanding --include=*.ts and printing 'no matches found', which reads as grep returning zero hits. Because the rule forced a positive control first, the artifact surfaced as an instrument failure instead of shipping as the finding 'L1 has no constitutional enforcement'. A discipline banked for one class transferred to another.", "valid_from": "2026-08-05", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-05-evening-the-brief-contained-the-failure-it-commissioned.md", "extracted_at": "2026-08-05"}
 {"subject": "the verbatim-containment prover with inversion-built controls", "predicate": "prevention", "object": "Caught a defect careful reading had already passed over. The INC-2026-07-28-01 jurist package returned 16/17 on first run: my quotation of chamber-library CLAUDE.md was a COMPRESSION wearing quotation marks, having dropped 'and opens with a Grounding section that QUOTES the ratified sections it builds on' — the clause that makes the requirement substantive. I had written, read and approved that sentence. 11/11 inversion-built controls absent, so INSTRUMENT VERIFIED and the failure was real.", "valid_from": "2026-08-05", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-05-evening-the-brief-contained-the-failure-it-commissioned.md", "extracted_at": "2026-08-05"}
 {"subject": "Constitutional Constraint 1 (~/CLAUDE.md)", "predicate": "has-no-mechanism", "object": "Verified 2026-08-05: settings.json carries no `permissions` key at all (deny 0, allow 0); the sole PreToolUse hook (verify-before-compose.sh) is scoped `*chamber-library*` at lines 24-28 and structurally cannot fire on ~/CLAUDE.md or ~/REVIEWED.md; the only friction is a symlink artifact that MEMORY.md documents as routable. The word is 'cannot', not 'must not'. Filed PENDING-107 [ESCALATE]; independent verification requested because the executor is not a disinterested reporter of limits on its own conduct.", "valid_from": "2026-08-05", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-05-evening-the-brief-contained-the-failure-it-commissioned.md", "extracted_at": "2026-08-05"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "ASSERTED-FROM-THE-RECORD-INSTEAD-OF-THE-SUBSTRATE, FIVE TIMES IN ONE SESSION. The hook's scoping; 'BMF is down' read off MEMORY.md; 'the two of you' one message after being told it was us; the backlog as cause of the prompt tax; the queue never draining. Every one was caught by MEASURING, three only because the steward pushed back. Recurred all day INSIDE the item documenting relayed unchecked claims.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-the-note-that-said-it-could-not-happen.md", "extracted_at": "2026-08-06"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "ATTRIBUTED-A-CAUSE-WITHOUT-RUNNING-THE-AVAILABLE-COUNTERFACTUAL. Claimed a 10,485-item backlog caused the 3.11s hook tax and 'fixed' it by parking the queue. Latency after: 3.11s \u2014 unchanged. The test (remove the alleged cause, measure the effect) cost one command and was not run before the claim. A plausible mechanism is not a measured one.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-the-note-that-said-it-could-not-happen.md", "extracted_at": "2026-08-06"}
+{"subject": "a record asserting that a control is ABSENT", "predicate": "drift-pattern", "object": "IS ITSELF LOAD-BEARING AND MUST BE VERIFIED LIKE ANY OTHER CLAIM \u2014 it is the note that stops future checking. project-L1-reliability.md:45 said '\u26a0 No KeepAlive \u2014 a crash leaves it down silently'. Inverted: the plist (unmodified since 2026-03-07) carries KeepAlive{SuccessfulExit:false}, so a crash RESTARTS it and only a clean stop leaves it down. The 08-04 kill therefore resurrected BMF; it ran 1d20h and neither party looked, BECAUSE the record said it could not happen.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-the-note-that-said-it-could-not-happen.md", "extracted_at": "2026-08-06"}
+{"subject": "pre-registering the predicted effect before measuring", "predicate": "prevention", "object": "Caught an overclaim in a DIFFERENT domain from the one it was banked for. The discipline was banked from census 01/02 (audits). Applied to a code measurement, it graded the executor's chavruta prediction WRONG ON MECHANISM: ~0.85 that queries would return EMPTY via conjunctive AND; actual = 0 empties, 26/27 crash at FTS5 parse. Without the written-first prediction, 'retrieval is weak' would have shipped as the finding and PENDING-97's filed description would still be believed.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-the-note-that-said-it-could-not-happen.md", "extracted_at": "2026-08-06"}
+{"subject": "the never-delete-on-failure rule in the drainer", "predicate": "prevention", "object": "A data-safety rule produced a DIAGNOSTIC finding it was not written for. Built so a failed POST never unlinks a queued observation, plus a halt after 10 consecutive failures. On the first full run it self-stopped at 50/10,535 \u2014 and that halt is HOW the entity-pipeline finding surfaced (relationships=31556ms against a 30s budget, cursor held). A safety valve doubled as an instrument.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-the-note-that-said-it-could-not-happen.md", "extracted_at": "2026-08-06"}
+{"subject": "BMF (bettermemories, localhost:3011)", "predicate": "operational-state", "object": "STOPPED AND DISABLED 2026-08-06 16:47 \u2014 launchctl bootout + disable on BOTH com.capablemind.bettermemories AND com.capablemind.bmf (the latter carries unconditional KeepAlive:true and would fight for port 3011 if loaded). disable persists across reboot, closing the RunAtLoad door the 08-04 kill left open. Verified: port closed, no agents loaded. Plists backed up, NOT edited. Revert: bmf-stop-and-keep-stopped.sh --revert. 10,485 observations preserved at ~/.capablemind/hook-queue-parked-2026-08-06 \u2014 do NOT resume draining until the entity pipeline is healthy.", "valid_from": "2026-08-06", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-06-the-note-that-said-it-could-not-happen.md", "extracted_at": "2026-08-06"}
+{"subject": "BMF (bettermemories, localhost:3011)", "predicate": "operational-state", "object": "down and staying down (2026-08-04 decision)", "valid_from": "2026-08-04", "valid_to": "2026-08-06", "confidence": 1.0, "source_file": "session-2026-08-06-the-note-that-said-it-could-not-happen.md", "extracted_at": "2026-08-06"}