session 2026-08-24 afternoon: the guards were not on the path

Session record + MEMORY.md promote/demote (prior Active Session relocated
verbatim to MEMORY-reference.md, md5 d6a53ddb, slice-not-retyped and verified
present). 11 KG lines: 5 drift-patterns, 3 preventions, 3 facts. 3 skill-harvest
proposals (a wake chamber conditional -- third instance of the same miss; the
wrap's Instruments field to report OBSERVED first firing per PENDING-156 (c);
the daily-note format defined in two places). 1 FIX-lane index line.

Pulling thread: the beacon, 2026-08-25 14:00 CEST, run ONCE -- which had no
trigger of any kind until tonight.

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

claude/memory/skill-harvest-register.md

@@ -492,3 +492,47 @@ longer safely one-directional — a vault-side spec now governs files a repo als
 **Classification: `[PROPOSAL]`** — changes what a skill *requires* (a gate before a destructive
 step), and the hard floor is engaged: silently reverting authorized work is exactly the
 "reduces what is surfaced to the steward" clause.
+
+### SHR-2026-08-24-a · A `/wake-up` chamber conditional — THIRD instance of the same miss
+**Status:** `PROPOSED` · **Firing moment: a named step in `/wake-up`** (the 77–83% tier), modelled
+exactly on the telos conditional already in §2.a.
+**Earned for the third time today.** `feedback-chamber-work-ground-in-constitution-charter-runbook`
+(steward directive 2026-07-28) says **any chamber work *or talk about it*** begins with touchstone /
+constitution / charter / runbook. This entire afternoon was chamber talk — the container question,
+the treatise, the conversion machinery — and **I opened none of the four until the steward said
+"read the runbook".** The cost was a proposal to build a second home for something already governed.
+The note itself predicted this: *"session-start prose has failed this class ≥4 times before, which
+is exactly why the existing hook was built"*, and the enforcement mechanism has been **owed since
+2026-07-28**.
+Proposal: a conditional in `/wake-up` §2.a in the shape of the existing telos one — *if the pulling
+thread or the steward's opening touches chamber-library / studium-engine / the corpus / the
+treatise, read the four and hold one line of the touchstone.* ⚠ Deliberately NOT the skill route:
+the note's own option (c) was `/chamber`, and **53 skills requiring executor recall measured 0%
+retrieval**. Routing to a wake step is the difference between 0% and 77%.
+**Classification: `[PROPOSAL]`** — changes what a skill *requires* at wake.
+
+### SHR-2026-08-24-b · `/wrap-up` — a mechanism does not count as BUILT until a first firing is observed
+**Status:** `PROPOSED` · **Firing moment: mechanically, at every wrap that built a mechanism** ⇒ a
+condition on the §8 Instruments field. **This is the skill-side of PENDING-156 option (c).**
+**Earned three times in two days**, each time on a tool with a green selftest: `vault-links.py`
+(08-23), `thread-query.py` (08-24 morning), `daybook-cue.py` (08-24 — 16/16 green, **wired to a
+matcher the work routes around, never fired once, `~/.claude/state/` did not even exist**). And the
+propagation is the point: daybook-cue **inherited the broken matcher by copy** from
+`verify-before-compose`, whose blindness was already on PENDING-95 — because that was filed as an
+*instance*, not a *class*.
+Proposal: the §8 Instruments field additionally reports, for any mechanism built this session,
+**whether a first firing was OBSERVED on the live path** — not that a selftest passed. Unobserved is
+a legitimate answer and must be stated as such, never rounded to "built".
+**Classification: `[PROPOSAL]`** — changes what the wrap *requires* before a thing may be called built.
+
+### SHR-2026-08-24-c · The daily-note format is defined in TWO places and will drift
+**Status:** `PROPOSED` · **Firing moment: mechanically, whenever the format changes** ⇒ one
+definition deriving from the other.
+`daybook-ensure.py`'s `SKELETON` writes the note; `/wrap-up` §7.5 enumerates the same headings for
+finalising. **Adding `## Corrections` today required editing both**, which is the field-computed-
+twice shape — the same class as the archive rule that produced a PASS-BUT-FALSELY on 08-23. Flagged
+in §7.5 rather than quietly patched.
+Proposal: §7.5 derives its shape list from `SKELETON` (or names it as the single source and stops
+enumerating). ⚠ **Derive from the CONSUMER, not the survivor** — the consumer here is the wrap step
+finalising a note the hook already created, so `SKELETON` is the natural source.
+**Classification: `[PROPOSAL]`** — borderline; the FIX lane says propose when in doubt.