Accept M2a follow-ups; M2a complete
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
@@ -6,8 +6,8 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
|
||||
|
||||
Boxmaker is a sovereign personal agent harness written in Rust. Work proceeds one milestone at a
|
||||
time (M0 to M7, table in `docs/milestones.md`). M0 (measurements) and M1 (workspace, `proto`, gate,
|
||||
`Decision`) are done. M2 is split: M2a (the inference path) is planned in `docs/plans/M2a/`,
|
||||
M2b (sessions, turn loop, `bxctl chat`) is not designed yet. Check `docs/implementer-log.md` for
|
||||
`Decision`) and M2a (the inference path: `inferproxy`, `loopd`'s HTTP, SSE and llama client,
|
||||
the startup self-test) are done. M2b (sessions, turn loop, `bxctl chat`) is not designed yet. Check `docs/implementer-log.md` for
|
||||
what is in flight.
|
||||
|
||||
- `docs/design.md` is the binding design brief. If it looks wrong or conflicts with a measurement,
|
||||
|
||||
Reference in New Issue
Block a user