review: M5c-2 review, lessons T59 and T60, and the gate-count rule
Co-Authored-By: Grok 4.6 <noreply@x.ai>
This commit is contained in:
@@ -27,11 +27,14 @@ links as code in `gatewayd`, the invalid-arguments reason, `bxcore::secrets`, on
|
||||
daemon; spec `docs/specs/2026-09-26-m5b-hardening.md`, 14 tasks) is done and merged, reviewed in
|
||||
`docs/implementer-log.md` and checked on straylight against the owner's Mattermost; the device
|
||||
check found that the self-test overran `inferproxy`'s burst (fixed in review). M5c is Honcho,
|
||||
through the owner's `roncho` (v1.0.0 on crates.io; `docs/specs/2026-09-25-roncho-requirements.md`),
|
||||
and is next, with no spec yet; M5d is the scheduler. P22 (proposed, not applied) makes Boxmaker a fleet of
|
||||
through the owner's `roncho` (v1.0.0 on crates.io; `docs/specs/2026-09-25-roncho-requirements.md`
|
||||
and `docs/specs/2026-09-27-m5c-honcho.md`). M5c-1 (the write path) is done and merged, reviewed in
|
||||
`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 is the scheduler. 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 `~/src/boxmaker-m5b` is a clone built with `nix build`. The owner's Honcho
|
||||
on straylight, where `~/src/boxmaker-m5c2` is a clone built with `nix build`. The owner's Honcho
|
||||
client `roncho` is at `~/src/roncho`. 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 (on straylight,
|
||||
|
||||
Reference in New Issue
Block a user