You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MEMORY.md size gate: daily size line in the token check-in + hard cap with offload in memory curation #2139
MEMORY.md measured 63,479 bytes (~16K tokens) at check-in #5 — it sits in every run's preload. The weekly memory-curation practice already checks size (Drew's note), but growth is daily, the ≤600-char rule caps bullet length rather than count, and the offload step is optional, so the file regrows between Sundays.
Do:
daily-token-usage-checkin body: add MEMORY.md bytes to its file-size snapshot (it already flags >55KB — make the byte count a standing line in every check-in report, with the 5 longest bullets named as offload candidates when over the cap below). Apply via the cron-definition workflow (definition file edit + cron.update with the complete body, then cron.view to verify).
memory-curation-review body: add a HARD CAP of 40,000 bytes — when MEMORY.md exceeds it, offload the longest topic blocks to ~/memory/topics/.md leaving one-line pointers (same information, smaller preload) until under cap, and report what moved. Same definition workflow + verification.
Acceptance: both definition changes verified by read-back; the next daily check-in reports the byte count; MEMORY.md at or trending to ≤40KB within one curation cycle.
DONE 2026-10-29 ~01:2x CDT, via the git-definition route (Drew's directive: edit the files in the git repo, post as replacement jobs, no scheduler body reads):
memory-curation-review — definition edited in hatch-personal (workspace/cron.d, commit 30dd057a) and posted as a replacement job: now DAILY at 20:12 (was weekly Sun), carrying (a) the hard cap — MEMORY.md maximum 40,000 bytes; (b) STEP 0 size pass on every run: offload longest topic blocks to ~/memory/topics/.md with one-line pointers until under cap, offload-never-delete, stop at the cap (averages between daily cleanups are accepted by design); (c) the SINGLE-OWNER rule — this job alone diets MEMORY.md; every other job appends and moves on; (d) Sundays keep the full curation practice, other days run the size pass only. Verified live: scheduler shows daily@20:12, next run Thu 2026-10-29 20:12 CDT.
daily-token-usage-checkin — definition edited and posted: MEMORY.md byte count is now a standing line in every check-in report, flagged when over the 40,000-byte cap. Next run Thu 2026-10-29 09:12 CDT carries it.
First cleanup happens tonight at 20:12 (MEMORY.md stands at 63,479 bytes vs the 40,000 cap — the pass offloads ~23KB of topic bulk to topics/ files with pointers).
Activity
developing-today commentedon Oct 29, 2026
CODE-1037
dezren39 commentedon Oct 29, 2026
DONE 2026-10-29 ~01:2x CDT, via the git-definition route (Drew's directive: edit the files in the git repo, post as replacement jobs, no scheduler body reads):
Closing as done.