David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

session 2026-09-09: REVIEWED-136 + AMD 1, the Tarbuckle fortnight read, PENDING-180, and the session record

Browse Source 
The lapsed 2026-09-08 obligation, closed. Session memory, ledger, KG (7 lines),
skill-harvest proposals A and B, and the demote-on-promote of the 09-06 Active
Session block into MEMORY-reference.md.

Pulling thread: an unruled record is read as ruled — which is not a replacement
for the floor but what the floor cannot measure.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TbXpZup4GGCbLBbRJ79KpM
This commit is contained in:
David F Glidden
2026-09-09 20:28:37 +02:00
co-authored by Claude Opus 5
parent 98bbf6055d
commit 025e40933e
7 changed files with 331 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/skill-harvest-register.md
+13
View File
@@ -655,3 +655,16 @@ skill's own instruction is to treat a borderline call as `[PROPOSAL]`.
step that *describes* an action rather than naming the executable form, and is therefore re-derived,
differently, each time it runs.
**Awaiting:** steward authorization.
## Proposed 2026-09-09 — from the Tarbuckle fortnight sitting
| # | Proposal | Kind | Firing moment (declared) | Status |
|---|---|---|---|---|
| A | **`governance-drift-check.py` validates a `text-present` needle at parse time** — warn when a trigger's needle is ALREADY present in its target file, i.e. the deferral came due the instant it was filed. | patch (script, not skill) | **MECHANICAL** — the checker already parses every block; this is one comparison at parse time. Fires without anyone remembering. | PROPOSED |
| B | **Reconcile `daybook-cue.py`'s message with `daybook-ensure.py`'s skeleton.** The cue says *"give what just landed its own `##` heading"*; the skeleton writes five fixed `##` sections. Following the cue appends siblings BELOW the structure, and the five sections stay empty until the wrap fills them from a compacted context — the exact reconstruction the log exists to replace. | patch (hook message) | **RITUAL** — the cue itself, which already fires every 15 min. | PROPOSED |
**A — why it is worth a mechanism rather than a discipline.** Earned by instance, self-caught: the deferral filed today to protect PENDING-168's count used the bare needle `PENDING-168`, which already occurred 3× in `REVIEWED.md` from REVIEWED-136's own text. It reported COME DUE on arrival. ⚠ **A trigger that fires immediately is indistinguishable, at a later wake, from a trigger that fired correctly** — it enters the come-due list and is read as a real obligation. The check is cheap and the failure is silent, which is the profile the routing table sends to a mechanism rather than a skill. ⚠ **Bound:** it can only detect the *present-on-arrival* case, not a needle that is merely too broad; and `text-present` takes one needle and cannot be OR-ed, so a ruling filed in a minority header form still evades a correct needle (censused 2026-09-06: 80 em-dash, 3 parenthetical, 1 joint, 1 slash).
**B — why the cue, not the executor.** Followed literally four times today; the structure stayed empty until §7.5. Not a recall failure — the instruction and the artifact disagree, and the instruction is the thing that fires.
**NOT filed, and why.** *"Leak-gate any working copy before committing, when the original is under a deletion order"* is a real discipline earned today (it stopped a verbatim corpus copy entering git permanently). It belongs on the **verification ladder**, which is **FROZEN under REVIEWED-123** — no additions from any source, whatever its authorization, until the trial is graded. It therefore **queues in PENDING-141's owed-entries list** and is not added. Recorded explicitly because a discipline this load-bearing is exactly the kind someone adds believing the freeze cannot have meant *this* one.