session 2026-08-13: fr identification pass, PENDING-135/136 filed and ruled, voice_stamp built; memory + register + KG

2026-08-13 21:28:46 +02:00
parent 92d5ad2547
commit e90c334bb2
6 changed files with 328 additions and 9 deletions
@@ -121,6 +121,56 @@ both still **needing dates, not "later."**

 ## Chronological log

+### 2026-08-13 — the fence was never blocked; the fr cell all but closed
+
+**REVIEWED-118 EXECUTED** (`e51e30d`) — authorized 2026-08-10, unexecuted for three days, found by
+substrate-checking the `**If AUTHORIZED:**` clause rather than reading it as status. L926's
+instances 6/12/16 retracted. Two decisions not implied by the ruling: `mauss-phase2-spans.yaml` is
+**generated**, so the record went into `scripts/bind_mauss_spans.py` too (a retraction in the
+emitted YAML alone is erased by the next run, with no diff); and that file measures **binding**, so
+the binding facts stayed and a cross-reference carries the retraction.
+
+**THE (b1) IDENTIFICATION PASS RAN** (`docs/fr-reported-speech-identification-pass-2026-08-13.md`),
+authorized at REVIEWED-116 pt 5 on 08-10 and never executed. **Reported speech in exactly 1 of 9 fr
+grounded spans** (L1551). The other eight are Mauss's own terminology, three self-marked
+(*"comme nous proposons de les appeler"*). ⚠ **Corrects REVIEWED-116 pt 6 rather than confirming
+it**: Mauss's 73 inline ≥120-char spans are a different population from the grounded set, of which
+only L926 and L1551 were ever members — **within the grounded set P7's F4 tagging was correct and
+complete.** ⇒ **PENDING-134's blast radius on inherited fr gold is ONE span.**
+
+**PENDING-135 (c) → REVIEWED-119 · PENDING-136 (c) → REVIEWED-120** (`de1c34b`, both placed by the
+steward). Instance 8 reclassified negative-candidate, marked in place; ⚠ **sub-type name OPEN** —
+§7.4(i) addresses the nested voice served *as* the host's, this **fuses** both. Count fields now
+carry their populations; bare `distinct_spans` retired. ⚠ **REVIEWED-119 pt 4 corrects PENDING-135's
+own blocking claim**: option (d) is constrained by `studium/v2-gold@1` §14.2 (`lines: [a,b]`) —
+**engine-side, D-1** — not by the chamber-locked `studium/meta@1`. Materially cheaper route.
+⚠ **I committed 136's own error while executing it**: `bound_instances_grounded` 12 by subtraction,
+ignoring instance 17. Correct **10**; all counts now verified by enumeration.
+
+**`voice_stamp` BUILT** (`d411034`; `engine/voice_stamp.py`, suite 22; fleet **9 suites / 285**).
+⚠ **AND MOVE 1 WAS NEVER BLOCKED.** PENDING-131 (c) is real for the **sidecar** and never bound the
+engine — `chunker.py` has recorded `char_range` document offsets since Cluster A. **The
+line-granularity ceiling was an artifact of where the fence was being WRITTEN, not of what the
+engine can SEE.** Paragraph-scoped pairing (not line-scoped) is what makes it work on hard-wrapped
+sources. **Reporter, deliberately NOT wired to abstention** — verdict semantics are unruled.
+
+**fr cell as of this wrap:** 11 listed spans / **8 grounded** (1 A + 7 B) / 2 reclassified / 1
+retracted / **10** grounded bound instances. **`ratio_A_to_B` VOID** — re-derived ONCE after
+PENDING-134 lands and all dispositions are recorded (REVIEWED-116 pt 5).
+
+⚠ **INSTRUMENT LESSON, and it is the day's most transferable:** the nested-voice census carried
+**five defects** and **four escaped its own controls** — every control was drawn from Mauss, so they
+exercised one quotation convention and one line structure, and could not see blindness to ASCII
+quotes (3 sources) or to hard-wrapped text (2 sources), both of which produced **clean zeros**.
+Only the fifth — a regression in an already-covered case — was caught by the controls. **A control
+set drawn from one source establishes nothing about a corpus.**
+
+⚠ **PENDING-134's remaining blocker is a STEWARD CLIENT RESTART, not a build.** `governance-mcp.py`
+builds `FILES` at import, so the four V0-lane keys registered at `4c3758e` are not yet served.
+Executor half discharged: selftest 54/54, and two key descriptions that had gone stale the same day
+were refreshed (`92d5ad2`) so the jurist's first read is not of a stale index.
+
+
 *Append substantive moves here at `/wrap-up` — not only to "Current state" above. A tracker with two
 update surfaces drifts between them (skill-harvest #183).*