session 2026-07-24 (evening): PENDING-71/72 + REVIEWED-72/73 (both jurist-ruled) + evening session memory + KG drift-patterns + skill-harvest

This commit is contained in:
David F Glidden
2026-07-24 14:50:37 +02:00
parent 1bbfbe0379
commit 54b8b5bf29
8 changed files with 123 additions and 6 deletions
+3
View File
@@ -434,3 +434,6 @@
{"subject": "claude-code", "predicate": "drift-pattern", "object": "capability-block-asserted-from-recall-not-tested", "valid_from": "2026-07-24", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-24-afternoon-levi-scale-pilot-ratified-flag1-gates-wave.md", "extracted_at": "2026-07-24"}
{"subject": "claude-code", "predicate": "drift-pattern", "object": "substitute-weaker-known-damaged-anchor-for-stronger-obligation", "valid_from": "2026-07-24", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-24-afternoon-levi-scale-pilot-ratified-flag1-gates-wave.md", "extracted_at": "2026-07-24"}
{"subject": "claude-code", "predicate": "drift-pattern", "object": "propose-governance-action-without-reading-its-own-declared-data-first", "valid_from": "2026-07-24", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-24-afternoon-levi-scale-pilot-ratified-flag1-gates-wave.md", "extracted_at": "2026-07-24"}
{"subject": "claude-code", "predicate": "drift-pattern", "object": "under-read-own-measurement — treated an accountable/declarable residual as a FAILURE. I had run (3) = 99.97%/0-interior-loss/0-boundary in my OWN measurement and dismissed it, assuming a clean PASS needs a ZERO residual; the 287-token delta was declared injection, excusable via the PENDING-69 moved_to shape. Also conflated two problems ('verifies markup not words'): shared-reader (structural) vs markup-noise (Flag-1 fixed it) → leaned (b). Jurist overruled → run (3) IS the ruled design; Flag-1 right-but-insufficient. Recurrence of assert-from-derived-not-substrate at the read-your-own-data layer.", "valid_from": "2026-07-24", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-24-evening-pending71-72-jurist-packages-ruled-reviewed72-73.md", "extracted_at": "2026-07-24"}
{"subject": "claude-code", "predicate": "drift-pattern", "object": "peer-mirror-extant-legacy-canon-as-precedent — inferred 'Warde needs no sidecar' from legacy typography PEERS (Bringhurst etc., pre-constitution) and built Warde's frontmatter by mirroring Bringhurst, which predates the schema, so the copy lacked lang/canonical/work. Steward corrected 2×: 'we cannot use the extant canon as precedent.' Build to the CONSTITUTION (spec/graduation-spec schema), never to what a legacy canonical looks like; the legacy-witness principle applied to graduation method.", "valid_from": "2026-07-24", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-24-evening-pending71-72-jurist-packages-ruled-reviewed72-73.md", "extracted_at": "2026-07-24"}
{"subject": "claude-code", "predicate": "drift-pattern", "object": "consequence-trace-one-level-shallow RECURRENCE — quoted REVIEWED-64 (the coordinate contract) in the PENDING-72 package yet failed to apply it to sections[], the very field I was proposing; sections[] IS one of the five line-carrying coordinate-contract families → needs a line_frame declaration. Jurist supplied the miss. Same shape as the jurist-package say-do-seam / consequence-trace disciplines I already carry — quoting a clause is not tracing its application.", "valid_from": "2026-07-24", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-24-evening-pending71-72-jurist-packages-ruled-reviewed72-73.md", "extracted_at": "2026-07-24"}