🔧 Auto-commit from sysupdate on 2026-07-05 22:41

claude/memory/skill-harvest-register.md

@@ -325,3 +325,17 @@ The single place proposed skills live so they don't evaporate between sessions.
 | **MEMORY.md deeper-reduction** (proposed 2026-06-08, condition-gated) | **CONDITION NOW MET — authorize the focused pass** | The 06-08 proposal deferred the risky deeper reduction "only if 157KB still trips 'only part loaded'." Tonight the index is **204.5KB vs a 24.4KB load limit** and a PostToolUse hook actively demanded compaction to ~17KB mid-wrap. NOT executed (the proposal explicitly names it "its own focused pass, not a tail-of-session move" — steward-unauthorized). Evidence is now decisive: ~88% of the index doesn't load at wake. Recommend authorizing the focused pass (compress archived one-liners further + move stable reference sections to a consult-on-demand `MEMORY-reference.md`; backup first, as 06-08). | PROPOSED (trigger met; awaiting steward authorization for a dedicated pass) |
 
 *(Two, neither manufactured: the first is the strongest evidence yet for an already-standing proposal plus one earned authoring rule; the second converts tonight's hook pressure into the governed channel rather than a tail-of-session mutation of real memory.)*
+
+### Harvest 2026-07-05 (V0 ratified + exclusion path + repo CLAUDE.md files)
+
+**BUILT + AUTHORIZED + COMMITTED this session:**
+- **`chamber-library/CLAUDE.md`** (`2238b65`, local — skemantix push pending) + **`studium-engine/CLAUDE.md`** (`4ad82d6`, pushed) — steward-authorized 2026-07-05. The two missing project-local orientation docs (ARC already had one; steward-flagged the gap). Pointer-style by design: they carry the *stable* layer (disciplines, governance posture, terminology, tool-fleet groups, layout) and delegate current-state to the trackers they name (corpus-work-map / PENDING / graduation-spec.yaml for chamber; rebuild-plan / charter for the engine). Chamber = governed (NOT D-1); engine = D-1 with the one V0 jurist exception.
+
+**PROPOSED (awaiting steward) — how to keep the CLAUDE.md files fresh:**
+
+| Element | Kind | One-line | Where it lands | Status |
+|---|---|---|---|---|
+| **`/wrap-up` — CLAUDE.md freshness check** | `/wrap-up` patch | At session close, ask: did this session change a **tool** (fleet add/remove), a **discipline** (a tool-evolution-log entry that generalizes), a **governance rule** (a PENDING/REVIEWED shifting posture), or a **term/mechanism** (like the exclusion path today)? → update the relevant repo `CLAUDE.md` line. **Event-based, NOT count-based** (the steward proposed a change-count threshold; challenged: these are POINTER docs, so most repo churn — files graduated, sources pinned, reports regenerated — doesn't touch them; a count fires on noise and misses the real triggers). Rides the §1.6 harvest slot, which already asks "did we change something that should be recorded?". | `~/.claude/skills/wrap-up/SKILL.md` | **BUILT 2026-07-05 (steward-authorized)** — §1.6 4th bullet + provenance note; mechanical-updates-apply / discipline-changes-surface split |
+| **CLAUDE.md staleness canary (git tripwire)** | create (small) OR git hook | If the `scripts/` set or `graduation-spec.yaml` changed but `CLAUDE.md` didn't since, flag "may be stale." Bounded, low-false-positive — the two most CLAUDE.md-relevant change classes. **Prompts; never auto-writes** (a bot rewriting the disciplines is the automation-of-recognition risk — the loop stays load-bearing). Sibling of the proposed **wake-canary** (MEMORY.md pointer-resolution). | git pre-commit / a `/repo-doc-canary` | **PROPOSED (optional; pairs with the wake-canary)** |
+
+*(Two proposals + two docs built. The freshness mechanism is the load-bearing one — it answers the steward's live question and applies this whole session's thesis [storage isn't memory; a protocol that exercises it is] to our own orientation docs. Not manufactured: the docs were just built, so the "how do they stay true" question is real and now. The count-vs-event correction is the substantive contribution — a raw threshold would institutionalize decorative maintenance.)*