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

session 2026-07-17 (afternoon): v2.1.0 landed OPERATIVE; 2b forks ruled by jurist; substrate-drift caught+corrected

Browse Source 
Session file + ledger (returns incl. the substrate-drift, jurist ruling) + KG (v2.1.0 fact, 2 drift/calibration lines) + skill-harvest (spec-supersession procedure; assert-X-in-Y→read-Y) + MEMORY.md/reference demote-on-promote.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E57CJHC6pH4XLqY4SHzJ3H
This commit is contained in:
David F Glidden
2026-07-17 21:52:46 +02:00
co-authored by Claude Opus 4.8
parent ed43422bbb
commit d734afb59b
6 changed files with 79 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/knowledge-graph.jsonl
+3
View File
@@ -380,3 +380,6 @@
{"subject":"claude-code","predicate":"drift-pattern","object":"re-derived-from-training RECURRED (drafted #2 as 'introduces the CTS-URN model' when §IV already ADOPTS it; §III/§VII/§IX already hold contract/registry/coverage) — caught by reading the actual spec. This time it got a STRUCTURAL fix: a PreToolUse hook (verify-before-compose.sh) DENYING un-grounded writes to chamber constitutional artifacts unless they carry GROUNDED-IN + Grounding. Prose lessons failed ≥4×; the hook fires at action-time. Steward-directed. See feedback-verify-before-compose-hook.","valid_from":"2026-07-17","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-17-constitution-block-drafted-whole-verify-hook-built.md","extracted_at":"2026-07-17"}
{"subject":"claude-code","predicate":"drift-pattern","object":"read-the-substrate-antidote FIRED repeatedly (reading §IV caught the #2 mis-frame; §VIII confirmed F-5; the roadmap caught 'finally'; substrate-check caught REVIEWED-58-not-fileable). Calibration: verify-against-substrate now catches overclaims when RUN — the remaining gap is running it BEFORE composing/claiming, which the verify-before-compose hook now enforces for constitutional writes but NOT for chat claims (where 'finally' slipped).","valid_from":"2026-07-17","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-17-constitution-block-drafted-whole-verify-hook-built.md","extracted_at":"2026-07-17"}
{"subject":"chamber-library-constitution","predicate":"state","object":"v2.0.2 OPERATIVE; #2 citation-amendment + #4 licence + #5 PREMIS RATIFIED (REVIEWED-60/61) + A3 (REVIEWED-59) awaiting an ATOMIC v2.1.0 landing; #1 wiring gated on residual-(b)/Region-4 (0 Loeb graduated); named-open frontier §II.3/§IX/promotion-criterion correctly-deferred.","valid_from":"2026-07-17","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-17-constitution-block-drafted-whole-verify-hook-built.md","extracted_at":"2026-07-17"}
{"subject":"chamber-library-specification","predicate":"operative-version","object":"v2.1.0 OPERATIVE (2026-07-17 supersession: #2 chamber-minted CTS-URN + Decision-1, A3 §Trust-Attestation, #4/#5 licence+PREMIS, F-5 §VIII pointer; REVIEWED-59/60/61; v2.0.2 frozen)","valid_from":"2026-07-17","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-17-v2.1.0-landed-operative-2b-forks-to-jurist.md","extracted_at":"2026-07-17"}
{"subject":"claude-code","predicate":"calibration","object":"read-the-substrate/surface-before-coding antidote fired at the DESIGN level (not just the claim level): orienting to BUILD the 2b wiring surfaced two genuine forks — and Fork 2's conditions had CHANGED that day (#2 landed) — so I held them for the jurist instead of coding a resolution from memory. On the governed side, overriding a light-gate-confirmed ruling is a governance act, not an executor call. The re-derived-from-training antidote generalizing from Q&A to build-design.","valid_from":"2026-07-17","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-17-v2.1.0-landed-operative-2b-forks-to-jurist.md","extracted_at":"2026-07-17"}
{"subject":"claude-code","predicate":"drift-pattern","object":"trusted-a-tool-docstring-a-derived-self-assessment-for-a-fact-that-lives-in-another-file — wrote 'build_loeb_sidecar is NOT in test_tools' into a jurist brief from the tool's own docstring, without grepping test_tools.py (which held the fact; 16 refs — it IS in the fleet). The claim OUTRAN the reading: I read the producer + gate + operative text and called that 'reading the substrate', but a claim ABOUT the tool's test-coverage is grounded in the TEST FILE, not the tool's self-description. This is (a) the chamber verify-against-substrate-not-the-derived-artifact discipline — which I QUOTED this same session — and (b) the CLAUDE.md contamination directive 'accept a component's self-assessment... and not ask whether it is honest', both violated. Caught by me at wrap (doc-currency), but AFTER the brief reached the jurist (immaterial to the ruling — luck, not diligence). Antidote: a factual claim's grounding must reach the file that HOLDS the fact, not one that merely describes it; when asserting X-is-in-Y, read Y. Steward-caught the say/do gap (I made a show of substrate-reading, then trusted a docstring).","valid_from":"2026-07-17","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-17-v2.1.0-landed-operative-2b-forks-to-jurist.md","extracted_at":"2026-07-17"}