session 2026-08-08 night: REVIEWED-99/100/101 placed; PENDING-117 amended + PENDING-118 filed; harvest #192 collision -> #194, #195 filed

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A35wiD55yRHj5U1ECZAX4t

claude/memory/knowledge-graph.jsonl

@@ -622,3 +622,8 @@
 {"subject": "three-party correction", "predicate": "drift-pattern-good-direction", "object": "RAN IN ALL THREE DIRECTIONS IN ONE DAY, which the differently-biased-checkers doctrine predicts but had not been observed doing. Jurist corrected executor (flat value -> two-job split). Executor corrected jurist (category placed in the convocation key), on evidence only substrate access yields. Steward corrected executor on a careless framing about language, which is what led to the L850 discovery. None of the three could have produced the result alone. Recorded as a single instance, proving nothing general — but the doctrine says to record evidence when it appears.", "valid_from": "2026-08-08", "valid_to": null, "confidence": 0.9, "source_file": "session-2026-08-08-voice-is-the-convocation-key.md", "extracted_at": "2026-08-08"}
 {"subject": "claude-code", "predicate": "drift-pattern", "object": "NAMED-A-REMEDY-CLASS-AND-CALLED-IT-DEPLOYED. Asked whether we could act rather than wait on a degraded instrument base-rate, I wrote 'act, don't wait' and listed three remedies — a pre-commit hook (an unauthorized PROPOSAL), a prospective-control count (a one-shot literal question that rotates out at the next wrap), and the ladder-ritual trial (MEASUREMENT, not a remedy at all). None was deployed. The steward's one-word challenge ('How?') was what exposed it. Rhetorical closure reads as mechanism precisely because a class plus three examples has the SHAPE of a plan. Test: for each named remedy, can you point at the thing that makes it fire without anyone remembering?", "valid_from": "2026-08-08", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-08-voice-is-the-convocation-key.md", "extracted_at": "2026-08-08"}
 {"subject": "a one-shot measurement", "predicate": "prevention", "object": "IS NOT A PRIME-DIRECTIVE VIOLATION, and treating it as one would have removed the thing that replaced guessing. Steward raised the worry 2026-08-08 after a bad week; the resolution is that the counterfactual for a one-shot script is an ASSERTION, not a durable instrument — so its visible fault rate is an improvement over an unfalsifiable hunch, not a decline. The real violation is re-writing what is already banked (a link-resolution canary typed inline the same day, though it lives in /wake-up AND on the ladder). Diagnosis: TOO FEW PROMOTED, not too many built — and only the first is actionable. Now measured as the K column of /wrap-up section 8's Instruments field.", "valid_from": "2026-08-08", "valid_to": null, "confidence": 0.9, "source_file": "feedback-one-shot-instruments-are-proportionate.md", "extracted_at": "2026-08-08"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "THE CHECKS ARE THE WEAK LINK, NOT THE WRITES — five instances in one session, every write sound on first attempt. `grep 'Instruments field'` against `**Instruments** field` · `tail -2` over a summary whose [FAIL] sat above the fold · inferring the tally's arithmetic instead of reading `total = len(_results)` · an induced-red probe anchored BELOW the counters it had to precede (3 false negatives) · a duplicate census counting MENTIONS including ones written seconds earlier. The unifying mechanism: EVERY ONE REDUCED THE OUTPUT BEFORE LOOKING AT IT (a count, a tail, an aggregate, an inference). A reduction cannot show its own miscalibration. Test before trusting any check: have I looked at this output unreduced, once?", "valid_from": "2026-08-08", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-08-night-the-checks-were-the-weak-link.md", "extracted_at": "2026-08-08"}
+{"subject": "the discrimination gate's BOTH-DIRECTIONS requirement", "predicate": "prevention", "object": "CAUGHT THE CONTROL'S OWN DEFECT, which a one-direction probe would have misread as a code defect in three suites. The induced-red probe injected its failing check below the tally lines, so suites capturing `total` into a variable exited 0 while still printing the failure — red_names_failure=False on navigate/retrieve/verify_quote. Requiring BOTH red-names-it AND restored-is-clean is what localised the fault to the probe rather than the code. Banked lesson (REVIEWED-83 A1 / ladder gate-design) stopping a DIFFERENT failure class: instrument self-fault, not the property under test.", "valid_from": "2026-08-08", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-08-night-the-checks-were-the-weak-link.md", "extracted_at": "2026-08-08"}
+{"subject": "the corpus-to-engine binding surface", "predicate": "has-enumeration-defect", "object": "FOUR SURFACES, NOT THREE. The governed record (graduation-spec.yaml engine_source_binding) names manifest.yaml sha256, sidecars source_sha256, coverage-ledger.json. The READING INDEX is a fourth consumed surface and NOTHING HASHES IT: measured 2026-08-08, content_sha256 occurs 0 times in the Alexander index's 689 lines, source_sha256 occurs 3 times and binds OUTWARD to the canonical text, and the manifest carries only a path plus a prose `reading_index_status`. Consequence: a three-sha checker would have read GREEN for all 56 days of the partial Alexander re-anchor (2026-06-12 to 2026-08-07, chamber 177e2b3). The binding runs index->text; nothing binds to the index.", "valid_from": "2026-08-08", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-08-night-the-checks-were-the-weak-link.md", "extracted_at": "2026-08-08"}
+{"subject": "a differently-positioned reader", "predicate": "drift-pattern-good-direction", "object": "BROKE THE EXECUTOR'S SCOPE WHERE THE EXECUTOR'S OWN CHECKS COULD NOT. The steward supplied one datum the item had not cited (chamber 177e2b3) and required it resolved before ruling. Resolving it produced a THIRD answer neither of the steward's two branches predicted: the commit did not touch the binding surface (so the framing stood) but revealed the enumeration the proposal rested on was incomplete. Second same-day instance of the doctrine's positive case; recorded as evidence, proving nothing general.", "valid_from": "2026-08-08", "valid_to": null, "confidence": 0.9, "source_file": "session-2026-08-08-night-the-checks-were-the-weak-link.md", "extracted_at": "2026-08-08"}
+{"subject": "governance-drift-check.py", "predicate": "has-blind-spot", "object": "DOES NOT READ ~/PENDING-archive.md, so its wake line 'deferred decisions: N tracked, none due' is a census of deferrals IN ONE FILE while reading as a census of deferrals. Every deferral inside a CLOSED item is invisible — and that is the normal case, because an item is typically closed BY a ruling that defers part of what it proposed. Surfaced only because a chamber YAML cited PENDING-53 and the citation failed to resolve live. Filed as PENDING-118 [HARDENING]; family with PENDING-108 and PENDING-110 — the register's own instruments not reaching parts of the register. Size unmeasured by design.", "valid_from": "2026-08-08", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-08-night-the-checks-were-the-weak-link.md", "extracted_at": "2026-08-08"}