session 2026-08-07: N1+R0+N2 built, @3 corrected under PENDING-111, D-5 recorded, two governance checkers, V2 unblocked

2026-08-07 18:11:16 +02:00
parent 97ae59a0d3
commit 2bdd40749a
6 changed files with 200 additions and 8 deletions
@@ -42,6 +42,9 @@ Split out of [MEMORY.md](MEMORY.md) on 2026-07-06 to keep the wake-loaded index

 # Archived sessions + stable reference layer (relocated verbatim from MEMORY.md, 2026-07-06)

+## Archived (2026-08-06 evening — the asterisk that carried meaning; demoted on promote at the 2026-08-07 wrap)
+- [Session 2026-08-06 evening — the asterisk that carried meaning](session-2026-08-06-evening-the-asterisk-that-carried-meaning.md) — **The parse fix LANDED (`27b79ca`): 26 crashes → 0, MISLOCATED 0, FALSE-POSITIVE 0** across all 5 items where silence is the correct answer — both deciding buckets empty, so the revert condition was not met. **HIT 0/22**: the engine now grounds nothing *honestly*, needing 13–19 terms to co-occur. **0/22 is the number to beat.** ⚡ **The embedding arm already scores 22/22 recall@20 on the identical items** — capability measured in June, never landed; V2 is the gate that makes surfacing it safe. **Governance: the register could not answer "how many rulings do I owe"** (23, not the digest's 26) — REVIEWED-87→94 placed, five of them **reconstructions** with provenance lines; PENDING-99/-105/-106 closed (106 **by split**); PENDING-108/-109/-110/-111 filed. ⚡ **The steward's printed A Pattern Language found that `fidelity_equivalence@3` erases Alexander's invariant rating** (81/114/54 across the corpus) — jurist package filed, containment 13/13. **Instruments caught 4 corrections; the jurist 1; the steward 2 — and his came from reading a physical book.**
+
 ## Archived (2026-08-06 — the note that said it could not happen; demoted on promote at the 2026-08-06 evening wrap)

 > ⛔ **NEXT = the chamber PARSE FIX — decided jointly with the steward at the 2026-08-06 wrap, not defaulted into.** Make `engine/retrieve.py` accept a sentence; 26 of 27 real questions currently **crash**. Bounded, and it carries its own regression test (27 audited queries with known answers). ⚠ **Inherited constraint, load-bearing: the fix must NOT make the engine answer more.** Every obvious fix (strip punctuation, tokenize, add semantics) trades **loud failure** for plausible-but-wrong — the incident's exact behaviour. Read `studium-engine/docs/chavruta-retrieval-measurement-2026-08-06.md` §2 and §4 **first**: PENDING-97's filed description of the bug is wrong (you never reach conjunction; the query dies at parse).