Commit Graph
2 Commits
Author SHA1 Message Date
David F GliddenandClaude Opus 5 bb8b974ffd session 2026-09-09 night: REVIEWED-137 verdicts sitting + PENDING-180 [FIX] executed
Session record, ledger merge, Tarbuckle tracker entry, 7 KG triples.
Pulling thread: the unit of the measurement is not the unit of the claim.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BsN7nKHjKBsn5bfNRRCNmo
2026-09-09 22:24:24 +02:00
David F GliddenandClaude Opus 5 2171d9127e [FIX] MEMORY.md load-integrity breach: relocate workstream state to its trackers
The wake reported MEMORY.md at 26,803 bytes against a 24,986-byte budget, so the
index was being silently truncated at load — the failure the two-file split exists
to prevent, on the one file every session reads first.

The cause was not bulk. It was an inversion the file's own Index discipline section
forbids: "Canonical Trackers as one-line pointers — chronological detail lives in
the linked tracker files, not here." Five tracker entries had grown into paragraphs,
and for three of them the index had become the SOLE custodian of live state:

  - Studium Engine: the tracker's chronological log stopped at 2026-08-13 while the
    index carried engine state through 2026-09-01 (REVIEWED-133, 496cd7e, the
    deleted undisclosed_days_in_force). Relocated verbatim as a dated log entry.
  - The Fool (Tarbuckle): the only linked target was a SEALED seed, which is not a
    place state may be appended, so there was nowhere for it to go. Tracker
    established (project-fool-tarbuckle.md); index line relocated verbatim.
  - L1 reliability: the tracker records that replay is "not resumable" but neither
    the mechanism (minCursor is a minimum over 11 modules, two never participate, so
    it is pinned at 0 by construction) nor the completion criterion (uninterrupted
    run length, not rate). Both appended.

Cut only where the file's own rule says to cut. "Rules that fire silently" was left
untouched by design — those entries keep their rule inline precisely because I would
not know to look them up, and gutting them is the one cut that would do real harm.
The frozen verification-ladder pointer (REVIEWED-123) and the skill-harvest hold
(PENDING-141) were likewise not touched.

Lossless-relocation gate applied: line-range slices, never retyping; md5 per slice;
token-conservation check over all five originals against the trimmed index and the
relocation targets — 0 unconserved after the L1 append. Link canary: 406 pointers,
0 dead, 0 mis-authored; 32 wikilinks clean.

26,803 -> 23,714 bytes. Headroom is only 1.3 KB; the Active Session block still
carries ~5.5 KB that the wrap rotates.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X3L79vgAnt1x2kxvf23Qt7
2026-09-03 08:34:03 +02:00