review: M5d-1 epochs and compaction
Co-Authored-By: Grok 4.6 <noreply@x.ai>
This commit is contained in:
@@ -32,8 +32,10 @@ and `docs/specs/2026-09-27-m5c-honcho.md`). M5c-1 (the write path) is done and m
|
||||
`docs/implementer-log.md`. M5c-2 (the read path: `recall` over the fleet and `ask_memory`, spec
|
||||
sections 3, 8, 9, 10 and 13) is done, reviewed in `docs/implementer-log.md` and checked on
|
||||
straylight against rift; no finding is open. M5d (scheduler and compaction, spec
|
||||
`docs/specs/2026-10-03-m5d-scheduler.md`) is approved, in two halves: M5d-1 epochs and compaction,
|
||||
then M5d-2 the scheduler. P22 (proposed, not applied) makes Boxmaker a fleet of
|
||||
`docs/specs/2026-10-03-m5d-scheduler.md`) is split: M5d-1 (epochs and compaction) is done,
|
||||
reviewed in `docs/implementer-log.md` and checked on straylight (spec 7); no finding is open.
|
||||
M5d-2 (heartbeat, cron, ToolSummary, live-slot isolation, unused `[compact] summarise`) is next.
|
||||
P22 (proposed, not applied) makes Boxmaker a fleet of
|
||||
independent agents, one per host, deployed with Nix in a last milestone, M8; `flake.nix` builds
|
||||
every binary, the tool image and a dev shell. Work happens on titan (macOS, no Nix); build and run
|
||||
on straylight, where a clone is built with `nix build`. The owner's Honcho
|
||||
|
||||
Reference in New Issue
Block a user