Review M3b tasks 14 to 17: accept; M3b done
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -10,9 +10,9 @@ time (M0 to M7, table in `docs/milestones.md`). M0 (measurements), M1 (workspace
|
||||
startup self-test) and M2b (sessions, the turn loop, `loopd serve`, `bxctl chat`) are done. M3 is split:
|
||||
M3a (`brokerd`'s decision path, spec `docs/specs/2026-09-18-m3a-decision-path.md`) is done and
|
||||
merged, reviewed in `docs/implementer-log.md`; its open findings (17, 18, 20, and 14, which M3b's
|
||||
first task must take) are listed there. M3b (the container runner and tools) is specified in
|
||||
`docs/specs/2026-09-22-m3b-runner.md` (a draft for review) and planned in `docs/plans/M3b/`
|
||||
(13 tasks, all testable offline); the image and the checks on straylight are the design model's.
|
||||
first task must take) are listed there. M3b (the container runner and the four tools, `docs/specs/2026-09-22-m3b-runner.md`) is done and
|
||||
merged: tool containers run from the image `deploy/tools-image.nix` builds, checked on straylight.
|
||||
M4 (`gatewayd` and Mattermost) is next to design.
|
||||
Straylight now serves Ornith as four slots over one 262,144-token pool; see
|
||||
`docs/inference-contract.md`, "Deployment change, 2026-09-20", before relying on cache behaviour.
|
||||
`docs/runbook.md` has an entry for every
|
||||
|
||||
Reference in New Issue
Block a user