session 2026-08-02 evening: Control Kernel v1.0→v1.1, reduction arm, CONTROL-A/B, trial 04 VOID, correlation 01

Session record, memory updates and KG appends for the evening session.

Filed: Control Kernel v1.0 (frozen, superseded) and v1.1 (governing); the
reduction arm and its two censuses; CONTROL-A and its defect twin with a
bidirectionally-gated ledger; trial 04 (CONTROL VOID) and its pre-registration;
correlation 01 — the first measurement of Constraint 6's own falsifier, jurist
4-of-6 and Fool 0-of-6 with no overlap.

New feedback memory: removing a claim is not the same as removing the reliance on
it. Earned by finding that draft 3's "fix" to CONTROL-A had CONCEALED a defect
rather than closed it — invisible to me, the kernel and four gates, found by a
differently-formed reader.

Verification ladder: the discrimination gate — a check must return different
verdicts on two REAL artifacts, one with the property and one without.

6 KG lines: two drift-patterns, one good-direction, two preventions, and the
Constraint 6 first-measurement.

claude/memory/knowledge-graph.jsonl

@@ -527,3 +527,9 @@
 {"subject": "absence-of-a-check-must-not-be-representable-as-the-safe-case", "predicate": "prevention", "object": "Found at three layers in one day and transferred forward at each: a shell pipeline returning 0 for 'could not look' (suppressed stderr made a missing git ref and a genuine sync identical); BackupOrchestrator.countUnprotectedEntries returning 0 for 'never backed up' (betterMemories_app#176); and then written INTO the L2 amendment as CheckerPosition's 'unknown' default, which must never be 'observed'. The L1 bug became the worked instance the L2 proposal cites.", "valid_from": "2026-08-02", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-02-pm-the-transfer-landed-and-the-vignette-was-a-diagram.md", "extracted_at": "2026-08-02"}
 {"subject": "arc-vignette", "predicate": "governing-anchor", "object": "The facade of Notre-Dame de Paris (steward, 2026-08-02): for the unlettered it gave the knowledge they could not YET read, WITHOUT interpretation. A biblia pauperum delivers structure without proposition — no caption names a figure, yet order, rank, centrality and seriousness arrive. Resolves how the vignette gives symbolic territory while protecting the reader from interpretation: MEANING LIVES IN THE SYNTAX, NOT THE LEXICON. Marks stay undecodable; the arrangement is grammatical. A diagram invites decoding; asemic writing refuses it while remaining inscribed. NOT IN THE SPEC — searched, zero hits — and the single most render-determining constraint the document lacks.", "valid_from": "2026-08-02", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-02-pm-the-transfer-landed-and-the-vignette-was-a-diagram.md", "extracted_at": "2026-08-02"}
 {"subject": "gitea-push-backlog", "predicate": "superseded-diagnosis", "object": "Recorded for weeks as 'blocked on VPN'. False for git: port 22 is filtered (ssh times out), 443 works — ARC pushes to gitea fine over HTTPS. The dotfiles gitea remote is SSH and its repo is EMPTY (nothing ever pushed); a one-line remote set-url to HTTPS is the fix, pending credentials. Steward confirms only the M4 needs the VPN, not the pushes.", "valid_from": "2026-08-02", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-02-pm-the-transfer-landed-and-the-vignette-was-a-diagram.md", "extracted_at": "2026-08-02"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "REMOVING-A-CLAIM-CONCEALS-THE-RELIANCE — I found an unsupported sentence in my own control document, reported removing it, and actually dropped the QUALIFIER from the obligation instead. The dependency survived, now implicit. Invisible to me, to the frozen kernel, and to four mechanical gates; found by a differently-formed reader (Fable) on a blind read. The deliberately-defective twin carried the EXPLICIT version of the same error and the concealed one is what survived review. RULE: the test is not 'is the bad sentence gone' but 'does the conclusion still need it'.", "valid_from": "2026-08-02", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-02-evening-the-control-was-not-sound.md", "extracted_at": "2026-08-02"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "CHECK-CERTIFIES-CODE-WHILE-CLAIMING-RESULT, five more instances in one session, inside the instruments built to escape it: the trial-03 degraded guard (answer non-empty vs answer produced); three splitter defects found only by contact with real documents; §3.3 false-passing a package whose Part VII IS a collected limitations section; and the twin ledger asserting 'ground truth is the ledger' when its gate only ever established 'the ledger records every DIFFERENCE'. TWO OF THE FIVE were caught by the steward asking an ordinary practical question, not by any instrument.", "valid_from": "2026-08-02", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-02-evening-the-control-was-not-sound.md", "extracted_at": "2026-08-02"}
+{"subject": "claude-code", "predicate": "drift-pattern-good-direction", "object": "THE-DISCRIMINATION-GATE — a check must return DIFFERENT verdicts on two REAL artifacts, one known to have the property and one known to lack it. Same verdict on both = it has demonstrated nothing, however many synthetic fixtures it passes. Built and shown REJECTING the §3.3 pattern as it actually shipped (flagged=False on both a package that has a collected limitations section and a ruling that has none). Root cause it fixes: fixtures derived from the CHECK inherit the check's blind spot; derive them from the PROPERTY, and draw them from real artifacts.", "valid_from": "2026-08-02", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-02-evening-the-control-was-not-sound.md", "extracted_at": "2026-08-02"}
+{"subject": "pre-registration-written-before-the-run", "predicate": "prevention", "object": "Trial 04 did NOT repeat trial 03's fatal prompt/document interaction, because its pre-registration reasoned about the PROMPT and not only the document and the grading. The anti-echo clause was predicted inert on an A-free document and was inert across all six runs. Trial 03 died of exactly this omission one session earlier; writing the omission into the next pre-registration as a section stopped it.", "valid_from": "2026-08-02", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-02-evening-the-control-was-not-sound.md", "extracted_at": "2026-08-02"}
+{"subject": "the directional-contamination rule, fixed before the read", "predicate": "prevention", "object": "Correlation 01's jurist score survived a live recall risk without special pleading, because the rule fixing how a high score may be used was written BEFORE the read: recall could only INFLATE, so a low score is robust and a high score needs the fresh context confirmed. Two behavioural controls then settled it from inside the result — the D3 miss (easiest defect to find by diffing, hardest by reading) and version-appropriate findings. Had the rule been reasoned out afterwards it would have been indistinguishable from rationalising a result I wanted.", "valid_from": "2026-08-02", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-02-evening-the-control-was-not-sound.md", "extracted_at": "2026-08-02"}
+{"subject": "constraint-6-differently-biased-checkers", "predicate": "first-measurement", "object": "Correlation 01, 2026-08-02: on one document with ledger-fixed ground truth of six defects, the jurist (Fable 5) found 4 and the Fool (Qwen 3.6 35B) found 0, with NO OVERLAP in what they caught — and the two converged only on the two defects the ledger did NOT record. No evidence of correlated misses, which is the condition CLAUDE.md states the doctrine would be falsified by. Limits: n=1 document, one pair, and both are formation-DIFFERENT readers, so it says nothing about the jurist-executor pair CLAUDE.md actually flags as untested.", "valid_from": "2026-08-02", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-02-evening-the-control-was-not-sound.md", "extracted_at": "2026-08-02"}