[PROPOSAL] PENDING-119 + PENDING-120: (e) is built, its wiring is not placed

119 — REVIEWED-101 condition 6 sends (e)'s consumer to ~/dotfiles/scripts/ on
cross-repo reasoning, while the same ruling's If-AUTHORIZED line says (e) needs no
cross-repo enumeration. The tension only became live because (e) was built as a
delegation to the gate that already enforced §1.1; a fresh sha-comparing script
would have made condition 6 straightforwardly right. Carries the finding that no
fleet suite validates live binding.

120 — the trigger's pathspec is corpus/ only, so engine/ and tests/ changes run no
suite. Demonstrated by the commit that built (e), which is also the first real
non-probe commit since the trigger landed: the hook ran and no declared check fired.

Both filed rather than fixed, on the steward's direction. PENDING-117 gains a
pointer-only AMENDMENT 2 so the thread is navigable from the ruled item.

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

claude/memory/session-ledger-2026-08-08.md

@@ -5,7 +5,7 @@ metadata:
   node_type: memory
   type: feedback
   originSessionId: 7d08dad4-626a-484c-870b-8f1a9674db7a
-  modified: 2026-08-08T11:54:21.195Z
+  modified: 2026-08-08T13:30:54.198Z
 ---
 
 # Session Ledger — 2026-08-08
@@ -93,6 +93,37 @@ metadata:
   from the start, which is what caught the probe's own anchor bug) · **0 duplicating
   something already banked**.
 
+### ⎯ SESSION 3 (context cleared ~15:25; same day, same ledger) ⎯
+
+- **T~15:3x — the day's pattern produced instances SIX and SEVEN inside the wake itself,
+  both at the error-vs-empty seam.**
+  (6) Answering the literal question, I ran `git log c86b825..HEAD -- corpus/` *inside
+  studium-engine*. `c86b825` is a **dotfiles** commit: the range died `fatal: Needed a
+  single revision`, and I read the empty stdout as "no commit touched the trigger path."
+  The conclusion happened to be true; the instrument was invalid. Caught **only** because
+  remedy (a) — state the check's vocabulary alongside its result — forced me to name the
+  range. Re-ran from `088a171` (the in-repo commit): result stands, now on a valid range.
+  (7) `ls <contamination-problem.md> && echo present` returned exit 2, no output. I was one
+  step from logging "the doc `~/CLAUDE.md` cites is absent" as a drift finding the checker
+  had missed. `find` located it at **exactly** the cited path.
+  **Unifying mechanism, sharper than yesterday's:** a *failed* command's empty output read
+  as a substantive *empty result*. Absence-of-output is not absence-of-thing. Five errors
+  yesterday reduced the output before looking at it; these two never had an output to
+  reduce and I treated the void as data. Instance (7) is the more dangerous kind — it would
+  have produced a **false positive against the governance record**, not a false negative.
+
+- **T~15:3x — literal question answered from the record, not introspection.** The
+  `.precommit-triggers` gate has **not** fired on any real commit: since `088a171`,
+  studium-engine has one commit (`4ec0ba2`, docs) and **zero** touching the declared
+  pathspec `corpus/ | scripts/run-fleet.sh`. This is silence-from-no-opportunity, not
+  silence-from-a-broken-path — the distinction the *silent net is uninformative* entry
+  requires be made before either reading is taken. The `--no-verify` half remains untested.
+
+- **T~15:3x — substrate-checked the resumption point rather than inheriting it.** Item (e)
+  verified **unbuilt**: `~/dotfiles/scripts/` does not exist; no `sha256`/`source_sha` match
+  anywhere under `~/dotfiles/scripts/` or `~/dotfiles/git/hooks/`. Global hook present and
+  active (`core.hooksPath = ~/dotfiles/git/hooks`, pre-commit 5.2k, 8 Aug 13:45).
+
 ## What held
 
 - The inherited prospective-control question (1 of 12) is carried forward as a live counter,