session 2026-08-08: post-wrap coda, one-shot proportionality memory, PENDING-116 in index

claude/memory/session-2026-08-08-voice-is-the-convocation-key.md

@@ -158,3 +158,44 @@ commit, and it surfaced only by accident. If the answer is *no* again, the remed
 proposed at §1.6 (extend the studium-engine pre-commit hook to run the fleet when
 `corpus/` or `corpus/sidecars/` changes) is what to build, and this is its second
 data point.
+
+
+---
+
+## CODA — after the wrap (the session did not end where the wrap did)
+
+**REVIEWED-98 placed and verified** (L1080, 8/8 load-bearing parts, no double-header).
+
+**The steward pressed on my base-rate answer — "How?" — and it was rhetoric.** I had
+written *"act, don't wait"* and named three remedies. Under challenge: **one was a
+proposal awaiting authorization, one was a one-shot I had described as standing, and one
+(the ladder-ritual trial) is measurement, not remedy at all.** Naming a remedy *class*
+plus three examples read as *deployed* when nothing was. Recorded as a drift pattern —
+rhetorical closure substituting for mechanism.
+
+**Then the steward asked the better question:** *"do we need so many single-use items?
+This seems to flow against our prime directive — but I honestly don't know."* Answer
+banked at [[feedback-one-shot-instruments-are-proportionate]]: **no** — a one-shot is
+proportionate to a question asked once, and its counterfactual is an *assertion*, not a
+durable tool. The violation is **re-writing what is already banked** (same day: I typed a
+link-resolution canary inline that lives in `/wake-up` AND on the ladder). *Too few
+promoted*, not *too many built* — and only the first is actionable.
+
+**Applied (FIX lane, three instruments discharged):** `/wrap-up` §8 now carries a standing
+**`Instruments`** field — *N run · M with a control written before first execution · K
+duplicating something already banked*. The **K column is the steward's question turned
+into a series** rather than left a worry.
+
+**Filed:** **PENDING-116** `[PROPOSAL]` — run the fleet on the change that breaks it.
+Design derived from *reading* the hook: `core.hooksPath` is `~/dotfiles/git/hooks`, so the
+hook is **tracked and travels** but is **global to every repo** → the trigger must be
+**repo-declared** (generative-from-spec, as the chamber already does). Costs stated up
+front: slower triggering commits · `--no-verify` bypasses it (a tripwire, not a boundary)
+· ⚠ **it does not close the cross-repo half** — a chamber-library edit can invalidate
+engine fixtures with **no engine-side commit at all**, so no hook fires on either side.
+That larger hole is named as an open follow-on, deliberately not absorbed.
+
+**A fourth check-vocabulary failure, same day.** My verification that the FIX-lane index
+line had landed grepped `Instruments field`; the line reads `**Instruments** field`, so it
+returned 0 against a line that was there. The write was fine; the *check* was wrong —
+again.