session 2026-08-08: REVIEWED-97 (vi disposition) placed + REVIEWED-98 draft; PENDING-114 authorized, PENDING-115 filed

This commit is contained in:
David F Glidden
2026-08-08 12:53:11 +02:00
parent 65ff40710d
commit 1a6cdf6cf1
11 changed files with 442 additions and 7 deletions
+8
View File
@@ -287,3 +287,11 @@ There is no mechanical detector for "you are about to act on a classification ru
(REVIEWED-95's trial sentence) — so this is the first entry filed *after* that home acquired a ritual.
**Recorded estimate: unknown, pending the 20-session trial.** If the trial grades below 60%, this entry
is evidence about the home, not about the lesson.
### 2026-08-08 wrap — one proposal, firing moment declared per the REVIEWED-95 gate
| # | Target | Kind | Content | Firing moment | Evidence | Status |
|---|---|---|---|---|---|---|
| 192 | `studium-engine/.git/hooks/pre-commit` (+ chamber-library's) | **extend an existing hook** — NOT a new skill | When a commit touches `corpus/` or `corpus/sidecars/`, run the test fleet and refuse on red. The hook already exists and already runs ("Pre-commit checks passed!"); it does not run the suites. | **Mechanical, and should always fire** — the top row of the routing table. Requires no executor recall, which is the whole point: the knowledge was already banked and still did not fire. | 2026-08-08. `118f411` split the Mauss `body` section into `body-01..13`, breaking `test_navigate.py`'s hardcoded node id. The fleet sat **202/203 red for a full day**, through **two separate rounds of correction to that very commit** (REVIEWED-96's findings, then the L850 discovery), and surfaced only because the steward asked an unrelated question about instrument base-rate. A sidecar edit is a *corpus* change that silently invalidates *engine* fixtures — the cross-repo binding surface studium-engine's own CLAUDE.md names as a re-anchor trap. | PROPOSED |
**Deliberately NOT proposed, and the reason is the finding.** The obvious second candidate — *"any one-shot script carries a positive control derived from the property, run before its output is read"* — **is already banked**, at `reference-verification-ladder.md` §Gate design: *"Derive fixtures from the property; draw them from real artifacts."* It is what diagnosed **both** of today's proxy-control failures. Filing it again would be duplication dressed as diligence. **The gap is the firing moment, not the knowledge** — which is PENDING-112's thesis, and this session is a third data point for the ladder-ritual trial rather than a reason to write a fourth copy of the rule.