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

Add pre-M1 design spec

Browse Source 
Threat model, data classes and provenance, approvals, IPC framing and
socket topology, the proto type list, log file rules, runtime layout,
the M1 gate, and how work is handed to the implementing model.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
kyle
2026-09-17 01:08:27 -07:00
co-authored by Claude Fable 5.1
parent 2a1fe5576c
commit afdac9ad3e
3 changed files with 287 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+3 -2
View File
@@ -13,10 +13,11 @@ for `AGENTS.md` and `Cargo.toml` to see whether M1 has started.
which also lists proposed changes that are not yet applied.
- `docs/inference-contract.md` holds the M0 measurements from straylight. Where it and the brief
disagree, the measurements are newer.
- `docs/specs/` holds design specs; `docs/plans/M<n>/` holds the task files Laguna works from.
- `spike/` is throwaway measurement code, not harness code.
Roles: implementation is done by Laguna S 2.1 through OpenCode on straylight, which reads
`AGENTS.md`. Design, specs, measurement and review are done here. Write plans for Laguna as small
Roles: implementation is done by Laguna S 2.1 (served by straylight) through OpenCode on this
machine, which reads `AGENTS.md`. Builds are deployed to straylight afterwards. 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.