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/session-ledger-2026-08-02.md

@@ -5,7 +5,7 @@ metadata:
   node_type: memory
   type: feedback
   originSessionId: 9256a5b3-c56b-4564-8ff2-8dc9d93ef97a
-  modified: 2026-08-02T10:55:01.684Z
+  modified: 2026-08-02T14:36:21.984Z
 ---
 
 # Session Ledger — 2026-08-02
@@ -44,6 +44,8 @@ metadata:
 - **Caught my own suppressed-stderr zero, in the sentence before reporting it.** Checking the gitea backlog with `git log --oneline gitea/main..main 2>/dev/null | wc -l` returned `0`, and I was about to report the mirror as in sync. The `2>/dev/null` made a *missing ref* and a *genuine sync* indistinguishable — `gitea/main` does not exist locally (`fatal: Needed a single revision`), so git errored and `wc` counted zero lines of nothing. Seventh instance of the day's pattern and the second self-caught one: **a failed check reporting the reassuring value.** Identical in shape to the `unprotected_entries: 0` guard clause found this morning and to the `'unknown'`-not-`'observed'` default written into the amendment this afternoon — three instances in one day, at three layers (a shell pipeline, an L1 orchestrator, an L2 schema). The gitea backlog is **unmeasurable from local refs** and remains owed and unquantified; the wrap's "nine commits" figure was not derived from a tracking ref.
 - **The wake's substrate-check rule fired a second time, on the thread itself.** Post-clear, checking the pulling thread's two checkable legs before restoring them found `amendments/` alive with 14 files. Cost avoided: opening the L2 transfer by *creating* a directory that exists, ignoring eight weeks of precedent and its naming convention — and telling the steward his repo lacks a phase it has been using. **This is a partial answer to the session's own literal question:** the census instrument that failed five times yesterday fired today when it was written into a *procedure* (the wake's §3 substrate-check step) rather than banked as a *lesson*. Provisional; one datum.
 
+- **2026-08-02 ~13:00 — second wake of the day; the substrate-check fired clean on the resumption point.** Before restoring the thread I checked its two premises rather than inheriting them: subnet first (this machine `192.168.1.52`, M4 on `10.0.1.x` — the exact confusion behind yesterday's three false "M4 is down" claims), then reachability (`ping 10.0.1.136` → 138 ms, up), then whether trial 03 had in fact never run (`fool-trial-01-…md` and `-02-…md` exist; no `-03-`). Both premises true, so the thread is **confirmed** rather than assumed. Cheap, and the cheapness is the point.
+
 ## Open horizons
 
 - **The Fool's false-positive control has never been run.** Until a *sound* document is run, the model's finding-rate cannot be distinguished from a production-rate — and trial 02's apparent restraint was an artifact of a disabled reasoning mode, not evidence of restraint.