David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

session 2026-09-20: PENDING-187 authorized, PENDING-139 AMD 1 (third blind spot), index rotation

Browse Source 
The cold-run framing retracted: /model-handoff §5 specifies report-and-stop and
a next phase from the artifacts, so the missing wrap was the protocol, not a
seam. Session memory, ledger, daily-note finalisation, and 8 KG lines (3 drift
patterns, 3 preventions, 1 blind-spot, 1 status).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
David F Glidden
2026-09-20 21:53:38 +02:00
co-authored by Claude Opus 5
parent 6c202ec823
commit 83d563350e
6 changed files with 251 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/knowledge-graph.jsonl
+8
View File
@@ -836,3 +836,11 @@
{"subject": "running code instead of reading it", "predicate": "prevention", "object": "CORRECTED THE JURIST'S ACCOUNT OF A DEFECT IT COULD ONLY OBSERVE, 2026-09-14. Reported as 'search surfaces ids the fetch tool cannot take'. Executing t_item showed the displayed head resolves byte-exactly; what fails is the natural truncation, because startswith(ident+' ') meets '1:' not '1 '. The defect is a colon. The reported form would have sent someone to build a new lookup path.", "valid_from": "2026-09-14", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-14-the-guard-was-path-keyed.md", "extracted_at": "2026-09-14"}
{"subject": "the 59-unattributable-blocks finding", "predicate": "prevention", "object": "PREVENTED MY OWN TWO AMENDMENTS FROM JOINING THE 59, 2026-09-14. Both were filed as '## PENDING-N — AMENDMENT 1:' (id+marker) rather than bare '### AMENDMENT'. Verified by the instrument: id+marker 19->21, attributable 41->43, NOT ESTABLISHED unchanged at 59. The morning's measurement applied to the afternoon's own filing.", "valid_from": "2026-09-14", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-14-the-guard-was-path-keyed.md", "extracted_at": "2026-09-14"}
{"subject": "claude-code-memory-write-guard", "predicate": "is-path-keyed", "object": "Claude Code's near-limit MEMORY.md reminder fires on the ~/.claude/projects/<proj>/memory/ SYMLINK path and NOT on the real ~/dotfiles/claude/memory/ path, though realpath is identical. Measured 5/5 vs 0/2, with the rival 'not near enough' excluded because the silent case was LARGER. Pre-registered and confirmed. Consequence: ALWAYS edit MEMORY.md by the symlink path.", "valid_from": "2026-09-14", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-14-the-guard-was-path-keyed.md", "extracted_at": "2026-09-14"}
{"subject": "claude-code", "predicate": "drift-pattern", "object": "CRITICISED A DELIBERATE PROTOCOL DECISION WITHOUT READING THE SKILL THAT GOVERNS IT. Called the cold Fable design session's missing wrap a seam — no session memory, tracker entry, daily note or commit. /model-handoff §5 specifies the opposite: report-and-stop, hand back, next phase FROM THE ARTIFACTS, because the load-bearing context lives in files not chat; the only wrap it contemplates is for a premium session that has begun to degrade. The steward overturned it in one sentence. Answer-from-training-before-the-banked-record, aimed this time at the steward's judgment rather than at a file — and the overstated version had already reached the daily note.", "valid_from": "2026-09-20", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-20-the-cold-run-was-the-protocol.md", "extracted_at": "2026-09-20"}
{"subject": "claude-code", "predicate": "drift-pattern", "object": "APPLIED A LIVE MEASUREMENT TO THE WRONG REFERENT AND IT WORE THE CONFIDENCE OF THE MEASURED FIGURES AROUND IT. Reported PENDING-187 and REVIEWED-140 as 'six days old'. They are three: dated 2026-09-17, today 2026-09-20. Six was the gap since the last wrap. Not a stale number — a correct number carried onto a different object without being recomputed, sitting in a paragraph of figures I had actually measured. The jurist caught it by noticing the Date field disagreed with my prose and named the gap rather than resolving it from one side.", "valid_from": "2026-09-20", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-20-the-cold-run-was-the-protocol.md", "extracted_at": "2026-09-20"}
{"subject": "claude-code", "predicate": "drift-pattern", "object": "WROTE A SELF-FALSIFYING SIZE FIGURE INTO THE INDEX WHILE CORRECTING THAT EXACT CLASS. Replaced MEMORY.md's stale '~24.1 KB; margin <=900 B' with a freshly measured '23,111 B / 105 lines' — and the same edit took the file to 24,116 B / 117 lines, so the new figure was false before the wrap ended. Correcting an instance does not inoculate against the class. Fixed by stating the RULE (measure, never read this number as current) instead of a number.", "valid_from": "2026-09-20", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-20-the-cold-run-was-the-protocol.md", "extracted_at": "2026-09-20"}
{"subject": "the jurist naming what it cannot check instead of guessing", "predicate": "prevention", "object": "TURNED AN UNANSWERABLE INTO A SAME-DAY MEASUREMENT, 2026-09-20. REVIEWED-140 row 4 held that the weight-delta design's holds table may be understated, contingent on whether PENDING.md/REVIEWED.md commits are atomic per entry — a fact the jurist said it could not check from where it sits. The executor, which has the substrate, measured it over 12 commits: NOT atomic (5 carried two entries, 1 carried none, several bundled 2-9 unrelated files). Row 4 is understated; the toy's hash-chained ledger is genuinely stronger than the register it models. Constraint 6 in its ordinary direction — the gap was closed because it was named rather than papered over.", "valid_from": "2026-09-20", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-20-the-cold-run-was-the-protocol.md", "extracted_at": "2026-09-20"}
{"subject": "committing an interrupted record unmodified before repairing it", "predicate": "prevention", "object": "PRESERVED A DIFFERENCE NOTHING ELSE IN THE REGISTER COULD HAVE, 2026-09-20. REVIEWED-140's three disposition fields disagreed; the executor committed that state as-is (73c1c6e) and left the repair to the steward's hand (fb02605). Within the hour the same session established that the register-integrity check CANNOT see an in-place rewrite of a placed ruling — its unit is the amendment block and such a rewrite leaves no block. So git history was the only witness, and only because the two acts were separated. The precaution looked fussy and was the sole mechanism.", "valid_from": "2026-09-20", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-20-the-cold-run-was-the-protocol.md", "extracted_at": "2026-09-20"}
{"subject": "the id+marker amendment form", "predicate": "prevention", "object": "KEPT A SECOND AMENDMENT OUT OF THE 59, 2026-09-20 — second consecutive session. PENDING-139 AMENDMENT 1 was filed as '## PENDING-139 — AMENDMENT 1:' with counts predicted before the write: 43/102/59 -> 44/103/59, NOT ESTABLISHED unchanged. A bare '### AMENDMENT' heading would have joined the very population the amendment is about.", "valid_from": "2026-09-20", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-20-the-cold-run-was-the-protocol.md", "extracted_at": "2026-09-20"}
{"subject": "governance-drift-check.py register-integrity check", "predicate": "blind-spot", "object": "Cannot detect an in-place rewrite of a placed ruling's disposition fields: its unit is the amendment-shaped block, and such a rewrite produces no block. Distinct in kind from PENDING-139's (A) and (B), which are marker defects repairable by regex. Filed as PENDING-139 AMENDMENT 1, 2026-09-20. Recommended remedy is option 2 (derive the check from git), explicitly NOT before PENDING-146 settles.", "valid_from": "2026-09-20", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-20-the-cold-run-was-the-protocol.md", "extracted_at": "2026-09-20"}
{"subject": "PENDING-187 governed weight-delta toy", "predicate": "status", "object": "AUTHORIZED by the steward 2026-09-20 via REVIEWED-140. Build at slice 1, D7 minimal cut (slices 1-4, scenarios S1-S5 and S9), with the §2.4 ts/entry_hash fix folded into slice 2 rather than gating slice 1. Design doc: dotfiles/claude/governance/governed-weight-delta-toy-DESIGN-2026-09-17.md (51,885 B).", "valid_from": "2026-09-20", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-20-the-cold-run-was-the-protocol.md", "extracted_at": "2026-09-20"}