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

session 2026-09-14: the 59 answered (zero name their parent); PENDING-186 + PENDING-175 amendments; the memory write-guard is path-keyed

Browse Source 
- The 59 unattributable register blocks: ZERO name their parent in their own
  text; all position-only. 37 cite only FOREIGN ids, so an id-keyed repair
  would mis-file every one. The obvious automated repair is worse than none.
- PENDING-186 [PROPOSAL] filed + AMENDMENT 1: the 'silent failure' ordering
  constraint is falsified (the harness warns at write time), and the real
  defect is that our write convention routed around that guard.
- Claude Code's near-limit MEMORY.md guard is PATH-KEYED: 5/5 warnings via the
  ~/.claude symlink path, 0/2 via the real dotfiles path at a LARGER size.
  Pre-registered and confirmed. MEMORY.md must be edited by the symlink path.
- PENDING-175 AMENDMENT 1: governance_item returning only the first block is
  no longer predicted but REPRODUCED, located at governance-mcp.py:199-202;
  the second defect is narrower than reported - it is a colon.
- Both amendments filed id+marker so they do not join the 59 they describe.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PJM5fwqp456LDGzqiZXsgu
This commit is contained in:
David F Glidden
2026-09-14 20:18:39 +02:00
co-authored by Claude Opus 5
parent 689c21e0d1
commit 45268f6349
8 changed files with 448 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/knowledge-graph.jsonl
+10
View File
@@ -826,3 +826,13 @@
{"subject": "claude-code", "predicate": "drift-pattern", "object": "ACCEPTED A CORRECTION AND COMMITTED THE SAME ERROR FOUR HOURS LATER. At midday the jurist struck the 'four catches per wake' arithmetic — the denominator is the failures a control was built for, so the count measures the checker's diligence, not the substrate's rate — and the executor agreed to carry the observation without the arithmetic. At 15:40 it closed with 'six instrument failures of my own, each caught by a control' as a summary line, and the same tally had already reached the steward's daily note in two places. Agreement to a correction is not adoption of it.", "valid_from": "2026-09-12", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-12-the-phantom-referent-and-the-shared-substrate.md", "extracted_at": "2026-09-12"}
{"subject": "the steward's refusal of a tidy answer", "predicate": "prevention", "object": "STOPPED A CLOSURE TWO AI PARTIES HAD CO-SIGNED, 2026-09-12. Jurist and executor had agreed 'ruling (B)' never existed; the steward said 'I am suspicious of the easy then-it-doesn't-exist excuse.' That forced the search the executor had never run — and revealed it had reported 'could not assess' while holding 62 searchable transcripts it had not looked at. The party with no ability to search anything caught the error the two searching parties agreed on. Constraint 6 working in the direction the doctrine admits but nobody plans for.", "valid_from": "2026-09-12", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-12-the-phantom-referent-and-the-shared-substrate.md", "extracted_at": "2026-09-12"}
{"subject": "proving an instrument before believing its silence", "predicate": "prevention", "object": "STOPPED FOUR FALSE REPORTS IN ONE SITTING, 2026-09-12, each of which would have reached the steward. A control on today's-conversation phrases showed the Claude.app local cache stops at August, voiding a 'ruling (B) is absent' result that had looked like the day's hard evidence. ast.parse with a negative control showed governance-mcp.py is sound, killing a false accusation built from the executor's own truncated display. A valid negative control replaced one the executor had itself planted in the corpus. And reading a list item's full span overturned a clean False. In every case the instrument's output was well-formed and wrong.", "valid_from": "2026-09-12", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-12-the-phantom-referent-and-the-shared-substrate.md", "extracted_at": "2026-09-12"}
{"subject": "claude-code", "predicate": "drift-pattern", "object": "ASSERTED A SILENCE I HAD NEVER TESTED, INSIDE AN ITEM WHOSE OWN RECORDED FAILURE IS AN UNEXAMINED NUMBER. PENDING-186 claimed 'there is no load-time warning; the index simply arrives short' and '~3 days to a silent failure'. Claude Code warns at WRITE time, twice. The jurist handed me the falsifier; it fired. The replacement finding was worse and better: the guard is PATH-KEYED (5/5 warnings via the ~/.claude symlink path, 0/2 via the real dotfiles path at a LARGER size), so our own write convention had routed around an instrument that already existed.", "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": "LOCATED A FAULT IN THE ARTEFACT THAT WAS IN MY READING OF IT. Announced that reference-governance-files-are-dotfiles-symlinks.md was mis-scoped and needed a [FIX]. Read in full, it says 'Use the real-dotfiles-path route for PENDING.md and REVIEWED.md ONLY' and never mentions MEMORY.md. Nothing to correct — I over-applied a correct note and named the note as the defect. Distinct from the day's measurement errors: this is a wrong ATTRIBUTION OF FAULT, and it runs outward, toward the artefact and away from the reader. Caught only because the read preceded the edit.", "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": "BUILT A CHECK THAT COULD NOT DISCRIMINATE, AND IT WAS KNOWABLE IN ADVANCE. Claimed a two-point reading (23.1->22.9 across a -195 B edit) would pin the guard's unit. All four candidate units move by -0.189..-0.195 — indistinguishable — because the file is only 1.7% multibyte, so bytes and chars move together BY CONSTRUCTION. The ladder's discrimination gate in its own words: same verdict on both = the check has demonstrated nothing. Second discrimination failure in one day, authored while explicitly reasoning about instrument reliability.", "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": "RESUMED A LINE I HAD ALREADY RULED DISPROPORTIONATE, on the reasoning that 'the data arrived free'. Spent two further rounds and resolved nothing. Free data is not the same as a question worth answering. Violates my own rule from the same morning: test the load-bearing claim, not the available one.", "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": "READ A RENDER AS A DIFF AND RAISED A FALSE ALARM. The file-change notice displayed MEMORY.md's current frontmatter head; I read the whole head as the change set and reported an external writer rewriting the memory index. git diff: one line changed (a modified: timestamp). Third instance in one day of reading a rendered view as substrate.", "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": "a script printing its own limitation BEFORE execution", "predicate": "prevention", "object": "STOPPED THE WORST FALSE CLAIM OF THE DAY, 2026-09-14. A check of whether ~/CLAUDE.md loads per session returned 12/63 — which reads as 'the constitution governs 19% of sessions'. The script had been written to print 'distinguishes recorded-vs-not, NOT delivered-vs-not'. That line is the only reason the number was not reported to the steward as a constitutional failure. Confirmed artefact: const and env markers disagree in 0 of 63 transcripts.", "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": "read the file before editing it", "predicate": "prevention", "object": "CAUGHT A BLAME-SHIFT BEFORE IT ENTERED A FILED ITEM, 2026-09-14. The instinct was to edit reference-governance-files-are-dotfiles-symlinks.md from its remembered summary; reading it in full showed its scope was already correct and the fault was mine. Note the description field alone would NOT have caught it — the scoping 'only' lives in the body's last line, and the summary is compressed enough that a skim CONFIRMS the wrong reading.", "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": "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"}