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

- 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

claude/memory/session-ledger-2026-08-24.md

@@ -0,0 +1,116 @@
+---
+name: Session Ledger 2026-08-24
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+---
+
+# Session Ledger — 2026-08-24
+
+## Returns
+
+- `2026-08-24T~wake` — **N-now re-measured, not relayed: 49/84, down from the 60 MEMORY.md carries.**
+  Ran the trial's own method (`len(TRANSCRIPTS.glob("*.jsonl"))`, `governance-drift-check.py:331`)
+  rather than repeating the banked figure. This is PENDING-147's rolling-window non-monotonicity
+  observed live: the ladder trial has moved **further** from its grading threshold overnight, not
+  closer. The banked number was not wrong when written; it is a point-in-time snapshot of a
+  counter that can fall. MEMORY.md's line is now stale and should be corrected at wrap.
+
+
+- `2026-08-24` — **Checked the typology before adding to it, and two of the three terms already
+  existed.** The steward proposed `compost heap` alongside `crucible` and `dynamo`. Rather than
+  compose a third figure, grepped first: **`crucible` is ratified architecture** — the Hearth, in
+  `00. Compass/…/12. Library — Attention & Meaning Ecology.md` v1.3.0, *"a zone where formal
+  classification is suspended during deep engagement"* — and **the compost heap was already banked
+  as the humic layer**, steward-verbatim 2026-04-21, built for authors rather than fragments.
+  Composing instead of checking would have created a second name for an existing figure, in a
+  system whose stated failure mode is exactly that. `dynamo` was **zero** in the live vault; left
+  as an open slot rather than guessed, and the steward glossed it mid-turn — *the turning of the
+  compost is the dynamo* — which dissolved a category error in the table I had already written.
+
+
+- `2026-08-24` — **Checked where the vault actually lands before moving private material.** The
+  flamenco file carries an explicit private-register clause and the chamber-origin disclosure.
+  Verified remotes first: the vault mirror pushes only to the steward's Gitea; `~/dotfiles` (where
+  the memory files already live) pushes to Gitea **and** `github.com/davidglidden/dotfiles`, which
+  checked `PRIVATE`. No exposure, and the harvest narrows the footprint rather than widening it.
+  The check was cheap and would have been the difference had the answer gone the other way.
+
+- `2026-08-24` — **Read the destination's own index before placing anything, and it changed the
+  job.** `09. Atlas of Roots` was not an empty folder needing a purpose; it is a fully specified
+  structure created 2025-09-29 that declares eight children — `places/pine-street`,
+  `people/moy-glidden`, `people/abg`, three themes — and contains none of them. Its purpose line is
+  *"living soil for Kai, Lune, and future descendants"*; its maxim is *"ensure grief remains
+  fertile, not stagnant."* **The steward's own soil metaphor, eleven months before this morning's
+  compost figure.** Placing the harvest anywhere else would have built a second structure beside a
+  waiting one.
+
+- `2026-08-24` — **The tool caught a link class my eye passed over.** Six new notes linked
+  `[[Atlas of Roots — Index]]`; the file carries a `00. ` prefix, so all six resolved dead. Exactly
+  yesterday's `NN. `-prefix class. Fixed with an alias on the index rather than six link edits —
+  the pattern the steward established on 2026-08-23 — and re-verified: dead 483 -> 475, zero
+  touching the harvest.
+
+
+- `2026-08-24` — **Corrected my own placement call after reading the files I had classified without
+  reading.** I had told the steward that all four "second bite" files wanted a home outside the
+  Atlas. On reading them, two are formation-level in their own words — *"what I have always tried to
+  do regardless of domain"* (the rules/poetic duality) and *"I've been moving towards this since
+  childhood"* (the long trajectory). Both went into the Atlas. **The classification had been made
+  from filenames and descriptions, not from the text** — the same shape as reading a field through
+  a summary instead of the substrate.
+
+- `2026-08-24` — **The link-class fired a third time and was fixed at the root rather than the
+  instance.** After the index alias, two more dead links appeared: the `08. Notes` pair link by
+  title (`[[Form true to itself]]`) while the theme files are hyphenated. Rather than edit two
+  links, added `aliases:` carrying the `title:` to **all ten** theme notes, which closes the class
+  for every link anyone writes naturally in future. Verified: 0 dead touching the harvest, vault
+  dead 483 -> 475, total links 2,200 -> 2,242.
+
+## What held
+
+- **Parsed frontmatter rather than grepping it**, for the status census (645 notes with
+  frontmatter, 373 declaring no status). The flag held on its fourth day, in the exact field class
+  that broke it three times on 2026-08-23.
+- **Verified the new links with `vault-links.py` (selftest 26/26) rather than by eye** — 0 dead
+  entries touching either note.
+
+- The wake read the substrate rather than the summary at the one place a false claim costs most.
+  The digest's `deferred decisions: 3 tracked, none due` was accepted only after the counter's
+  implementation was read, which is what surfaced the drop.
+
+## Open horizons
+- ~~Held back: `user-formation-flamenco-substrate`~~ — **steward authorized 2026-08-24 ("it is
+  crucial"); written as two themes, both marked private register in `assurance.risk_flags` and in a
+  visible block, so the boundary travels with the note.**
+- **Not written, and should not be harvested:** `people/moy-glidden` and `people/abg` — the Atlas's
+  declared core. Substrate exists in memory; the writing is the steward's.
+- ~~Second bite pending~~ — **authorized and done.** All 11 `user-` files harvested: 10 themes in
+  the Atlas, 2 notes in `08. Notes`, every memory file back-pointed. **Still open: the Atlas's
+  Places and People, which are the steward's to write.**
+- **How a heap is turned, concretely.** Darwin's answer was a container shaped like the current
+  work; the vault has no counterpart. Named in the new note as the most load-bearing of its four
+  open items.
+- **A fourth status value** (`composting`?) — the Frontmatter Spec anticipates one: *"a fourth
+  value later is a small, named decision, not a redesign."*
+
+- The literal question inherited from 2026-08-23: re-read Craig Mod's *A Swarm of Blood Robots*
+  in full and find what CONTRADICTS yesterday's conclusions, not what corroborates them.
+- Rebuild the vault status from trackers + substrate, not from last night's summary (steward
+  suspects it was incomplete; three same-shape instances yesterday).
+- Tooling/uses sweep.
+- Hub notes as **venues** for re-encounter — the load-bearing horizon under the pulling thread.
+
+## Confidence to recalibrate
+
+- Inherited, twice-earned: **the check is skipped precisely where confidence is highest.**
+- ⚠ **A quick grep is not a parser** — fired three times on 2026-08-23 on the same field class,
+  the third time *after* it had been named at midday. Knowing the pattern did not prevent it.
+  Today's Mod re-read is a reading task, but the vault-status rebuild is exactly the shape that
+  invites it. Parse; do not grep-and-report.
+- ⚠ **A substring is not a path** — `99. Archive` silently excluded 78 live notes. Live is 1,298.
+
+## Authorization moves
+
+## Sub-agent dialogues
+
+## Bypasses