---
name: session-2026-08-08-night-the-checks-were-the-weak-link
description: "Went underneath the pulling thread to build the mechanism it needs: the fleet is green and now runs on the change that breaks it (REVIEWED-100). Every write landed sound on first attempt and ALL FIVE of the day's errors were in CHECKS — grep vocabulary, tail truncation, inferred arithmetic, a probe anchored below its own counters, a census counting mentions. PULLING THREAD: the corpus↔engine binding surface enumeration is WRONG — three surfaces named, four actual, and the fourth is unhashed — and every stage REVIEWED-101 authorized consumes that enumeration."
metadata: 
  node_type: memory
  type: project
  originSessionId: 932b538a-4624-4ce7-8826-ecbd6b8d079f
  modified: 2026-08-08T13:08:23.437Z
---

# Session 2026-08-08 (night) — the checks were the weak link

Second session of the day, straight after a wrap. The steward's rulings on
PENDING-115/116 came first and reshaped the session before it started: they
turned an idle thread-blocked evening into an executable mechanism bite.

## PAST — what moved, and why

**The shape changed because a finding changed it, not because the authorizations did.**
Asked how 115+116 reshaped the session, I ran the fleet to confirm the red test and
read `tail -2`: `33/34 checks passed`. Nearly reported the fleet green — overturning a
*correct* banked finding on a bad read. Caught only because REVIEWED-100's design forced
the question *what is red, mechanically*. Exit codes: `exit=1`. **The summary enumerated
skips and not failures**, so the natural place to look showed a pass-fraction and a skip
roll-call while the `[FAIL]` sat above, unrestated. That, not the node id, was the finding.

**Step 1 — the fleet, `eef81fa`.** The Scolie is now reached **by title within the Mauss
work**, not by a hardcoded id: a curatorial re-split is legitimate and touches nothing the
containment check tests, and requiring exactly one such division keeps a vanished or
duplicated Scolie failing loudly. All seven suites now name failures in the summary;
exit-code logic untouched, so acceptance is bit-identical and only the report gained.
Proven by **induced-red discrimination on all seven**, both directions required.

**Step 2 — the trigger, `088a171` + `c86b825` (dotfiles).** `.precommit-triggers` declares
`corpus/ | scripts/run-fleet.sh`; the global hook stays repo-blind and delegates path
matching to git's own pathspec engine. Deliberately **dependency-free rather than YAML** —
`yq` is absent, the consumer is bash, and a global convention needing a toolchain silently
fails to travel. `scripts/run-fleet.sh` is new because **the repo had no canonical fleet
runner at all**, which is part of why running the suites depended on memory.
**Acceptance both directions:** a real `body-04` rename refused the commit and tripped
`test_every_drawer_is_reachable` (63 unreachable of 5779); a docs-only commit ran nothing.

**Three governance filings, two of them corrections of my own record.**
- **PENDING-117** (cross-repo) filed, then amended on the steward's conditions.
- **PENDING-118** split out per condition 5 — the drift checker is blind to archived
  deferrals; it belongs with PENDING-108/110 as *the register's instruments not reaching
  parts of the register*, and inside a [PROPOSAL] it would have died with its host.
- **#192 collision resolved** → **#194**, PENDING-116's citation repaired (it had been
  resolving to the wrong entry), the row's target corrected, status set **BUILT**.

## PRESENT — how it stood

**All five of the day's errors were in checks; every write was sound first time.**
`grep 'Instruments field'` against `**Instruments** field` · `tail -2` over a summary whose
failure sat above the fold · inferring `total`'s arithmetic instead of reading
`total = len(_results)` · an induced-red probe anchored *below* the counters it needed to
precede (three false negatives) · a duplicate census counting **mentions**, including the
ones I had written thirty seconds earlier. Not carelessness in the work: **reaching for a
check whose vocabulary I had not verified against the thing it must match.**

**Diagnosed sharply, and it is not a missing rule.** All five **reduced the output before
looking at it** — a count, a tail, an aggregate, an inference. A reduction cannot show its
own miscalibration. Two ladder entries already cover this (*state what you did NOT
establish*; *discriminate between two REAL artifacts*) and **both are scoped to checks that
ship**. Every failure was a check that didn't ship. **The exemption is the bug** — so the
remedy is a scope widening, and writing a third copy would be the actual violation.

**Steward chose remedy (a): state the check's vocabulary alongside its result.** Adopted
immediately and visible from that point on. It works by making *my* miscalibration
catchable by a **differently-positioned reader** rather than by me — which the evidence
favours: of the five, three were caught only because the work continued and forced me to
touch the thing again, one by implausibility, and exactly **one by design** (the both-
directions probe).

**The steward's ruling on 117 broke my scope, which was the useful outcome.** Their datum —
chamber `177e2b3`, a partial Alexander re-anchor undetected **56 days** — resolved into a
*third* answer, not the two they offered. It did **not** touch the engine binding surface
(one file changed, the reading index; zero under `canonical_texts/`; live canonical sha ==
declared `accf235d…`), so the item's framing stood **uncorrected**. But: **nothing hashes
the reading index** (`content_sha256` 0 occurrences in 689 lines; `source_sha256` ×3 all
pointing *outward*; the manifest carries a path and a **prose** `reading_index_status`).
**All three surfaces in (a)/(e) would have read GREEN for the entire 56 days.** The
enumeration is **four, not three** — and being wrong the moment it was written is the
sharpest argument for the steward's own condition 1: declared data, one home, never
hardcoded in a consumer.

**I also had a rejection resting on borrowed authority.** I rejected option (b) as *"exactly
the coupling REVIEWED-100 rejected"* — factually wrong (that was a *globally shared* hook vs
a repo-local declaration). Struck visibly in the amendment rather than swapped, because a
rejection's reasoning becomes precedent whether or not it was sound.

## FUTURE — what pulls

> **PULLING THREAD — the binding-surface enumeration is wrong, and everything
> REVIEWED-101 authorized consumes it.** Three surfaces are named in the governed record;
> four exist; the fourth (the reading index) has **no hash anywhere in either repo** —
> it binds outward to the text, and nothing binds to it. The spec amendment that makes the
> enumeration machine-readable is condition 1 of the ruling and gates (a) and (c). Until
> the enumeration is *true*, a checker built on it inherits the exact blindness that let a
> partial re-anchor live 56 days.

**ACTIONABLE RESUMPTION POINT (as of wrap — re-judge against what changed):**
```
0. Nothing half-finished. studium-engine main clean, PUSHED. Fleet 204/204, 7/7 exit 0.
   REVIEWED-99/100/101 placed; PENDING-115/117/118 open.
1. START WITH (e) — it is buildable NOW and needs no cross-repo enumeration:
   unconditional sha check on every studium-engine commit, in the hook already landed
   (~/dotfiles/git/hooks/pre-commit). Three engine-side surfaces: manifest sha256,
   sidecar source_sha256, coverage-ledger. Milliseconds. Placement per condition 6:
   ~/dotfiles/scripts/. Both-directions control required.
   ⚠ Re-verify the hook from the substrate — its only evidence is my own acceptance
     test from THIS session; do not inherit that frame.
2. THEN the graduation-spec amendment (condition 1, JURIST-GATED → /jurist-package):
   engine_source_binding prose -> structured `surfaces:` list, and it must carry FOUR,
   including a content hash for the reading index that does not yet exist.
3. THEN (a) scheduled checker, THEN (c) the reanchor repair tool.
4. SEPARATELY: PENDING-115 (a1)+(b1) before remediation step 3. (b1)'s control needs a
   two-voice fixture — the honest source is the REAL weil-gravity-and-grace sidecar
   (17 `voice: thibon` sections, unchunked only because citable:false).
```

**Other open horizons, ranked:**
- **[load-bearing, authorized]** the (e)→spec→(a)→(c) sequence above.
- **[load-bearing, authorized]** PENDING-115 (a1)+(b1). ⚠ `translation` carries the
  identical `ROLE_CLASS` gap, latent **by absence** (0 `role: translation` sections exist).
- **[the deeper thread, unruled]** the `quotation-in` × `translation-of` composition
  package — (vi) is still **decided but inapplicable**. Today went *underneath* it
  deliberately; it has not moved and still gates the Mauss remediation and V2's fr gold.
- **[open, unruled]** PENDING-118 (archived deferrals invisible to the checker).
- **[owed]** skill-harvest **#190–#193** + the ladder scope-widening (**#195**, filed
  tonight) — the dedicated short session the steward named.
- **[converging]** three open threads now sit on the Alexander canonical: PENDING-111
  (`fidelity_equivalence@3`, 293 escaped-emphasis instances), the R0 region-verification
  gap (0 verified by fingerprint), and this item.

**PAUSE STATEMENT:** I am putting this down at a genuine close — the mechanism bite was
taken all the way, both halves proven, nothing mid-arc, everything pushed. I stopped
*before* (e) deliberately: (e) modifies the same global hook I changed ninety minutes
earlier, whose entire evidence base is my own acceptance test from this session, and
building onto it now would let the second test inherit the first's assumptions. A cold
session re-derives that from the substrate. What I want to find still pulling is the
**enumeration** — because a checker built on a false surface list is the failure this whole
item exists to prevent, committed one layer up. The unease I carry is not about the work
but about the ratio: five errors, all in checks, on a day whose entire subject was checks.

**LITERAL QUESTION for next-Claude** *(checkable — the record answers it, not introspection)*:
**Did the `.precommit-triggers` fleet gate fire on a real, non-probe commit — and did it
catch anything?** Today it fired twice, both times on probes I staged myself. A gate whose
only firings are its own acceptance test has not been shown to work in the field; that is
precisely the *silent net is uninformative* class, turned on the net we just built. If the
answer is *it has never fired*, ask whether the trigger path (`corpus/`) actually matches
where corpus work lands, or whether `--no-verify` is being reached for routinely.