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

session 2026-08-24: the heap got a dynamo — thread-query.py + daybook-cue.py, 11 user-memories harvested to the vault

Browse Source 
- thread-query.py: the turning. Queries both corpora with the pulling thread, excluding
  the recency slice (/wake-up reaches 0.71% of an 859,803-word corpus) and favouring age.
  Wired into /wake-up §2.b.3, replacing a described-not-invoked grep step. Trial
  pre-registered, graded 2026-10-05 from --log. Caught PASS-BUT-FALSELY on its first live
  run at 14/14 green; rescored on windowed co-occurrence, length-bias control added.
- daybook-cue.py: PostToolUse cue for the daily note. Diagnosed from the record — the
  hook only ever CREATED and nothing ever prompted filling. 16/16, fail-open, never blocks.
- All 11 user-* memories harvested into the vault (12 notes, 10 into 09. Atlas of Roots,
  empty since 2025-09-29); each memory file back-pointed, vault note canonical for the idea.
- N-now corrected in MEMORY.md: 49/84, down 11 — the counter is a rolling window.

Steward-authorized. Trials: thread-query + Smart Connections, both graded 2026-10-05.

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-24 11:25:39 +02:00
co-authored by Claude Opus 5
parent e3da9abad1
commit edf71fb173
20 changed files with 1094 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/user-care-over-traffic-skills-as-accountability.md
+12 -1
View File
@@ -19,4 +19,15 @@ permalink: claude-memory/user-care-over-traffic-skills-as-accountability
- Cousin to the **Non-Convergence Principle** in `~/CLAUDE.md`: *"the system should be inhabitable, dignified, and sufficient at any point along the way"*; no step depending on a future step to be meaningful.
- Cousin to **"Would Alexander do it?"** feedback (2026-04-27): each pattern at a time, not bulk-scaffold; the cramped will of the maker is the failure mode.
- The audience-building diagnosis from the jurist (find the right 50 people; address RSS / email-capture gaps) sits *next to* this principle — practical, not prerequisite. The work answers to itself first; audience-building is a separate concern.
- When time pressure surfaces (e.g., 2026-04-28 jurist's "publish today"), don't compromise care for speed; the publish-today imperative still operates within the care-frame, not against it.
- When time pressure surfaces (e.g., 2026-04-28 jurist's "publish today"), don't compromise care for speed; the publish-today imperative still operates within the care-frame, not against it.
---
## HARVESTED TO THE VAULT — 2026-08-24
The steward's verbatim and the thinking now live in **`08. Notes/The work answers to itself.md`** ("The work answers to itself"), where they can be come
upon. **The vault note is canonical for the idea.**
This file keeps its own job — firing the rule at the moment it applies during a session — and is not
a second copy of the claim. If the two ever disagree about what the steward said, the vault note
governs and this one is corrected.