session 2026-08-20: Fool re-aimed to the seating question; trial 09 void; input-dependence-01 pre-registered

Session record, MEMORY.md rotation (prior Active Session demoted verbatim to
MEMORY-reference.md), Fool workstream tracker added, 7 KG facts appended,
3 skill-harvest proposals filed with declared firing moments.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JQKeKY9T9d95KpvHwwok8T
This commit is contained in:
David F Glidden
2026-08-20 23:34:22 +02:00
co-authored by Claude Opus 5
parent 03813cfb6d
commit f687e0e972
5 changed files with 263 additions and 8 deletions
+44
View File
@@ -448,3 +448,47 @@ two-clause test; **proposed rather than applied, per "when in doubt, propose."**
**Status: PROPOSED.**
**No FIX-lane changes were applied this session.**
---
## Proposed 2026-08-20 (wrap) — two, both with declared firing moments
### SHR-2026-08-20-a · PATCH `/wake-up` — reconstruct an unwrapped session before composing the briefing
**Status:** `PROPOSED` · **Firing moment: a ritual juncture that already exists** — the wake digest
*already* detects and prints `⚠ PREVIOUS SESSION DID NOT WRAP`. Today that banner fired, said
*"Not established: whether that session did work worth keeping. The transcript is on disk and can be
read if the gap matters"*, and then the briefing was composed anyway from a MEMORY.md that predated
the lost session. **The detector works; nothing consumes it.** Proposal: when the banner fires, read
the transcript and reconstruct the missing session record *before* composing the briefing, rather
than offering it as an option the steward must think to take. Earned today — nine hours of work
(a ratified vault spec, seven commits, a trial prepared-and-held) existed only in a `.jsonl` the
harness prunes at 30 days. **Routes to a named step in an existing ritual ⇒ high retrieval.**
**Classification: `[PROPOSAL]`** — changes what a skill *requires*, not only what it records.
### SHR-2026-08-20-b · CREATE a mechanical **cited-but-never-opened** detector
**Status:** `PROPOSED` · **Firing moment: mechanically, and it should always fire** ⇒ a hook or a
wrap-script check, **not** a skill. Earned by three instances in three days of the same failure, the
third *inside the document reporting the second*: a governance artifact asserted a claim about a
file it cited by path or hash and never opened in-session. Proposal: at compose- or wrap-time,
extract the file paths and sha256s a written artifact cites, diff against files actually read this
session, and flag the difference. **This is the one routing the harvest table calls for** — the
alternative is "a condition the executor must first notice", which the 2026-08-07 measurement puts
at ~10% retrieval and which has now failed three times running. **Classification: `[PROPOSAL]`** —
a new mechanism; and it touches what the executor may assert without checking.
### SHR-2026-08-20-c · PATCH `/wrap-up` §7 — the vault sync can now REVERT authorized vault work
**Status:** `PROPOSED` · **Firing moment: mechanically, every wrap** ⇒ a guard in the §7 step itself.
**Earned today, and only by accident.** §7 rsyncs `CapableMind-AI/docs/thinking/David/` →
`vault/08. Notes/CapableMind/thinking-mirror/`, one-directional. **Since 2026-08-19 the destination
is the edited side:** the vault frontmatter passes (spec v1.0.0, 511 edits / 268 files, steward-
authorized) touched files inside that mirror. Verified at this wrap — 14 files differ, and the
differences are the passes' own work, e.g. `related: DN-DRAFT-ungovernable-threshold` →
`related: "[[DN-DRAFT-ungovernable-threshold]]"`, which is §6's wikilink conversion. **A plain rsync
would have silently reverted it.** The sync did not run today only because the auto-mode classifier
blocked the command; the guard should not depend on that.
Proposal: before syncing, diff the trees; if the destination differs on files the source did not
change this session, **stop and surface** rather than overwrite. Also record that this mirror is no
longer safely one-directional — a vault-side spec now governs files a repo also writes.
**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.