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

session 2026-08-06: skill-harvest proposals 180-184, KG drift-patterns + preventions, session memory

Browse Source
This commit is contained in:
David F Glidden
2026-08-06 16:57:07 +02:00
parent 3b0730d593
commit f6fc59017a
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/skill-harvest-register.md
+12
View File
@@ -266,3 +266,15 @@ The single place proposed skills live so they don't evaporate between sessions.
| 179 | `/wake-up` §1 | patch | **When the wake digest reports a state that contradicts another line of the same digest, name the contradiction as unreconciled rather than choosing a reading.** Today's digest reported *"PREVIOUS SESSION DID NOT WRAP (ended ~Aug 04 19:43)"* alongside *"Last wrap: 1 min ago"*. Both cannot describe one session; the digest could report the fact and not reconcile it. I named it, but nothing in the skill required that, and the tempting move — silently picking the reading that fits — is the failure. | 2026-08-05 wake. Also the observable surface of PENDING-104 (concurrent sessions, no detector), so the patch is cheap evidence-gathering for a filed finding. | PROPOSED |
**Classification note:** both are `[PROPOSAL]`, not FIX-lane. #178 changes what a governed artifact (a jurist package) must assert — the assertion clause of the two-clause test. #179 is borderline (it *adds* visibility rather than narrowing it, so the hard floor is not hit), but the lane is provisional and the skill's own instruction is *when in doubt, propose*.
## New proposals (2026-08-06 wrap — the note that said it could not happen; awaiting steward)
| # | Target | Kind | Proposal | Earned by | Status |
|---|--------|------|----------|-----------|--------|
| 180 | verification ladder | new entry | **Run the counterfactual before attributing a cause.** Before claiming X causes Y, remove X and measure Y — where that is cheap and available. Not "is the mechanism plausible" but "does the effect survive the cause's removal." | 2026-08-06. Attributed a 3.11 s hook tax to a 10,485-item backlog and "fixed" it by parking the queue. Latency after: **3.11 s, unchanged.** One command would have refuted it before the claim. | PROPOSED |
| 181 | Symmetria §3 flag | new flag | **A record asserting that a control is ABSENT is load-bearing, and must be verified like any other claim — it is the note that stops future checking.** Sibling of `comments-promising-behavior`, but inverted and more dangerous: a doc that *overstates* a gate invites scrutiny; a doc that *denies* one closes the question. | 2026-08-06. `project-L1-reliability.md:45` said "⚠ No KeepAlive"; the plist has carried `KeepAlive{SuccessfulExit:false}` since 2026-03-07. The 08-04 kill therefore restarted BMF; it ran 1 d 20 h and **neither party looked, because the record said it could not happen.** | PROPOSED |
| 182 | verification ladder | new entry | **A piped command masks its exit code.** `script \| tail` returns `tail`'s status. When a script's exit code carries the verdict, do not pipe it — or read `PIPESTATUS`. | 2026-08-06. The drainer exits 1 on a halted run; piped through `tail`, the harness recorded **exit 0**. A signal that existed was discarded — the day's own theme, in the invocation. | PROPOSED |
| 183 | `/wrap-up` §1 | patch | **A tracker with two update surfaces drifts between them.** When updating a canonical tracker, append to its **chronological log**, not only its "Current state" section — or state explicitly that no substantive move occurred. | 2026-08-06. `project-L1-reliability.md` had **no 2026-08-04 entry** in its log, though 08-04 produced PENDING-92/93/94 and the session's central finding. Only "Current state" was touched. Found two days later, by accident. | PROPOSED |
| 184 | `/wake-up` + general | patch | **Before asking the steward to supply inputs, check whether the repo already holds them.** One level past `resurface-banked-notes-before-rederiving`: not re-deriving a banked *note* but re-sourcing banked *material*. | 2026-08-06. Was one keystroke from asking the steward to invent questions for the corpus, while `corpus/chavruta-ground-truth.yaml` held **27 real queries with audited answers** from his own hand-run chavruta. The steward caught it with four words. | PROPOSED |
**Classification note:** all five `[PROPOSAL]`, none FIX-lane. 180/181/182 add ladder/flag entries but each changes what the executor must *do* before asserting (the latitude clause). 183/184 change skill procedure. Lane is provisional; when in doubt, propose.