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

Update CLAUDE.md for the split docs and the Laguna handoff

Browse Source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
kyle
2026-09-17 00:22:44 -07:00
co-authored by Claude Fable 5.1
parent 06c05e0023
commit cbdaaa0d50
1 changed files with 16 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+16 -11
View File
@@ -4,19 +4,24 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
## Current state ## Current state
Boxmaker is a sovereign personal agent harness written in Rust. As of this file's creation the Boxmaker is a sovereign personal agent harness written in Rust. There is no Rust code yet. Work
repo holds only `docs/design.md`: no code, no Cargo workspace, no Makefile, and no git history. proceeds one milestone per session (M0 to M7, table in `docs/milestones.md`). M0 is mostly done;
Work proceeds one milestone per session (M0–M7, table in `docs/design.md` Part 3). Before doing check for `AGENTS.md` and `Cargo.toml` to see whether M1 has started.
anything, check which milestone artifacts exist (`spike/`, `docs/inference-contract.md`,
`AGENTS.md`, `Cargo.toml`) to work out where the project is.
`docs/design.md` is the binding design brief. Part 1 is the design; Part 2 is the session 1 prompt - `docs/design.md` is the binding design brief. If it looks wrong or conflicts with a measurement,
(M0 spike plus M1 skeleton); Part 3 is the milestone table and the per-milestone prompt template. stop and say so. Changes to it land as their own commit and are recorded in `docs/decisions.md`,
If the brief looks wrong or conflicts with a measurement, stop and say so. Don't work around it. which also lists proposed changes that are not yet applied.
Propose changes to `docs/design.md` as their own commit before building on them. - `docs/inference-contract.md` holds the M0 measurements from straylight. Where it and the brief
disagree, the measurements are newer.
- `spike/` is throwaway measurement code, not harness code.
Once they exist, read `AGENTS.md` (project standards, how to run the gate, how to verify against Roles: implementation is done by Laguna S 2.1 through OpenCode on straylight, which reads
straylight) and `docs/inference-contract.md` (M0 measurements) alongside the brief. `AGENTS.md`. Design, specs, measurement and review are done here. Write plans for Laguna as small
closed tasks: exact paths, given type signatures, verified crate APIs, tests specified first, and
"stop and report" instead of judgement calls. The model the harness serves is Ornith-1.5-35B-A3B.
The inference server is shared with other sessions. Before using Ornith slot 1 or sending unpinned
requests, check `GET /slots?model=ornith-1.5-35b-a3b` so you do not evict someone's cache.
## Commands (planned in M1, not yet present) ## Commands (planned in M1, not yet present)