session 2026-08-07 evening: PENDING-112 + REVIEWED-95 (route harvested capabilities by firing moment)

Register censused and rebuilt from the archive: 177 claimed -> 154 real live
proposals, legible, with exact archive:L### pointers. The 2026-08-01 compaction
was lossless but illegible (55 scraped header rows; 95% of cells cut mid-word);
completeness verified 124 = 124, so nothing had been dropped.

Skills pruned 63 -> 12 after measuring that 53 had never been invoked across 64
sessions / ~5 months. The finding underneath: retrieval is set by a capability's
HOME, not its importance -- MEMORY.md 83%, register 77% (named in a wake step),
ladder 14%, 'THE GOVERNING FRAME' 12%, 'Read at Step 0' 9%, recall-bound skills 0%.

PENDING-112 filed, jurist design-gated, steward concurred; REVIEWED-95 drafted.
Landed: the /wrap-up 1.6 filing gate (prospective) and the /wake-up ladder
sentence (a pre-registered trial intervention, landed alone). The 20-session
falsifier is WIRED, not intended -- DEFERRED-DECISION ladder-ritual-trial,
trigger: transcripts 84. Wiring it exposed two defects in the deferral checker:
no way to express a session count except as a date proxy, and a scan that never
looked at claude/governance/. Controls 16 -> 19.

Stroke 2's 41-entry ladder append deliberately NOT done: REVIEWED-95 Q3
sequences it after the ladder trigger, which now exists.

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

PENDING.md

@@ -1369,3 +1369,58 @@ Source: `chamber-library/canonical_texts/traditions/contemporary_voices/environm
 **Awaiting:** Steward routing to the jurist. Filed ≠ sent.
 
 ---
+
+## PENDING-112 — Harvested capabilities are routed by importance, not by firing moment; retrieval is set by home, and ranges 0%–83%
+
+**Date:** 2026-08-07
+**Tag:** [PROPOSAL] — routes to the **jurist** for design-gating, then the steward. It changes what the executor must do *before filing* a harvest proposal (the latitude clause of the two-clause test) and governs the disposition of all 154 open items in the skill-harvest register.
+
+**Summary:** We decide where a harvested lesson lives by asking how important it is. The measured determinant of whether it is ever read again is something else entirely — whether a ritual names it. Two files carrying the most emphatic labels in the memory system are reached in 9% and 12% of sessions; a file with no emphasis at all, merely named in a `/wake-up` step, is reached in 77%. Fifty-three skills requiring executor recall were reached in 0% across ~5 months.
+
+**Measured this session**, across the 64 transcripts on disk (~168 MB), counting access by any route (Read, Grep, Bash):
+
+| home | mechanism | reached |
+|---|---|---|
+| `MEMORY.md` | loads unconditionally + named wake step | **83%** (53/64) |
+| `skill-harvest-register.md` | named wake step (§2.a) | **77%** (49/64) |
+| `reference-verification-ladder.md` | pointed at from `MEMORY.md`; "reach for the gate the claim's shape demands" | **14%** (9/64) |
+| `project-chamber-versioned-releases.md` | labelled **THE GOVERNING FRAME for all library work** | **12%** (8/64) |
+| `the-chamber-touchstone.md` | labelled **Read at Step 0 of any chamber work** | **9%** (6/64) |
+| 53 skills requiring executor recall | present in the skill listing | **0%** (0/64) |
+| `/jurist-package` | recurring, self-announcing juncture | 16 invocations in 18 days |
+
+**Rationale — why this is structural and not a discipline failure.**
+
+*Emphasis does nothing; ritual naming does everything.* The strongest language available to us — "THE GOVERNING FRAME", "Read at Step 0 of any chamber work" — buys 9–12%. The register carries no emphasis and sits at 77%, and the only difference is that `/wake-up` §2.a contains the sentence "Read `skill-harvest-register.md` directly." This is the closest thing to a natural experiment our own data affords.
+
+*Age is ruled out as the cause.* `/jurist-package` (added 2026-07-20) has 16 invocations; `/model-handoff` (added 2026-07-22) has none. Same vintage, opposite outcomes. `audit` and `vault-update-people` have had **3.7 months** at zero.
+
+*Opportunity is ruled out in at least one case.* `/field-divergence-sweep` exists precisely for "two implementations of the same field disagree." That condition arose **this session** — `measure_rerank.py` and `navigate.py` had each grown their own reading-index reader and disagreed on 3 of 253 patterns with neither right — and the work was done by hand without the skill being reached for. The lesson *was* retrieved, because `feedback-derive-the-rule-from-the-consumer-not-from-the-survivor` sits in `MEMORY.md` and loads unconditionally. Same content, two homes, opposite outcomes, in one session.
+
+*This is why the register reached 154.* We harvest real lessons and file them, overwhelmingly, as things the executor must first notice and then recall. The harvest works; the retrieval does not.
+
+**The proposed rule.** Route a harvested capability by its **firing moment**, never by its importance:
+
+1. **Mechanically detectable and should always fire** → hook or wake/wrap script.
+2. **Fires at a ritual juncture that already exists** → a named step in `/wake-up` or `/wrap-up`.
+3. **A recurring workflow someone announces out loud** ("this needs to go to the jurist") → a skill.
+4. **Fires on a condition the executor must first notice** → **neither a skill nor a bare ladder entry.** Either find the mechanical detector and route to (1), attach it to the nearest existing ritual step, or accept ~10% retrieval **and record that estimate on the proposal itself.**
+
+**Filing gate:** a harvest proposal must declare its firing moment before it can be filed. Where none can be named, the proposal is documentation and must say so on its face. This is the clause that changes executor latitude, and it is why this is `[PROPOSAL]` rather than FIX.
+
+**Immediate consequence for an existing authorization — surfaced rather than executed.** Stroke 2 (2026-07-19) authorized appending *all earned ladder entries* to `reference-verification-ladder.md` wholesale; 41 rows in the rebuilt register carry that stamp. Executing it as written moves 41 harvested lessons into a **14%** home. The authorization is genuine, but it was granted before anyone had measured the ladder's read rate. The executor has not executed it and seeks direction.
+
+**Options.**
+- **(a) Adopt the routing rule and the filing gate.** Every new harvest declares a firing moment; those that cannot are marked documentation. Applies prospectively; the 154 existing items are re-routed opportunistically, not in a sweep.
+- **(b) Adopt the routing rule as guidance without the filing gate.** Cheaper, changes nothing enforceable — and on this session's own evidence, unenforced guidance is precisely what produces a 14% file.
+- **(c) Reject; continue proposing skills freely.** Consistent only if the 0%/9%/12% figures are held to be an artifact of the measurement rather than of the design.
+
+**Recommendation: (a)**, plus one act not requiring it — **give the verification ladder a ritual trigger**. The register went from unread to 77% by being named in a wake step; the ladder is the same kind of object with the same defect and no such sentence. That single change plausibly does more for the 41 Stroke-2 entries than appending them.
+
+**Confidence, graded.** *High* — recall-bound skills at 0% (53 skills × 64 sessions). *High* — age is not the discriminator (`jurist-package` vs `model-handoff`). *Moderate* — the 14%-vs-77% contrast: two files of different natures (a work queue versus a reference work), so the comparison is suggestive, not controlled. **Instrument caveat:** access counts come from grepping transcript JSON for tool-call targets; a file consulted from memory without a tool call is invisible to the method, which biases every figure *downward* and the recall-bound skills least of all.
+
+**Files affected:** `~/.claude/skills/wake-up/SKILL.md` (a step naming the ladder, if (a) or the standalone recommendation is authorized) · `~/.claude/skills/wrap-up/SKILL.md` §1.6 (the filing gate) · `skill-harvest-register.md` (a firing-moment column) · no change to any ratified spec.
+
+**Awaiting:** Steward routing to the jurist. Filed ≠ sent.
+
+---