kyle/boxmaker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

CLAUDE.md: M5a is planned

Browse Source 
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
kyle
2026-09-24 15:33:20 -07:00
co-authored by Claude Opus 5.5
parent de1032157b
commit 0062b2a895
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+3 -1
View File
@@ -18,7 +18,9 @@ and checked end to end against the owner's Mattermost; no finding is open. M4b (
Mattermost, spec `docs/specs/2026-09-24-m4b-approvals.md`, 18 tasks) is done and merged, reviewed
in `docs/implementer-log.md` and checked end to end against the owner's Mattermost, including an
approval asked by a non-approver; no finding is open. M5 (memory, then the scheduler) is split into
M5a, M5b and M5c by P17 to P20 (applied 2026-09-24); the M5a spec is next. The owner's Honcho client
M5a, M5b and M5c by P17 to P21 (applied 2026-09-24). M5a (local memory, `memoryd`) is specified in
`docs/specs/2026-09-24-m5a-local-memory.md` (approved) and planned in `docs/plans/M5a/` (15 tasks,
branch `m5a`); its reference is a bundle on straylight, `~/boxmaker-refs/m5a-ref.bundle`. The owner's Honcho client
`roncho` is on titan, not on this machine. Branches land on master by rebase and
fast-forward, never a merge commit. The owner's Mattermost settings and the
bot's token are in `mattermost.env` at the repository root: ignored by git, never committed, and