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

docs: M5b landed; CLAUDE.md and decisions follow

Browse Source 
decisions: M5b settles the invalid-arguments reason, tag
neutralisation and the shared secret store (their open rows go), and
the verdict on the run's two driver trials. CLAUDE.md's current state:
M5b done, M5c (Honcho, roncho 1.0.0) next; straylight's clone is
boxmaker-m5b.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
kyle
2026-09-27 19:15:09 -07:00
co-authored by Claude Opus 5.5
parent d423d87115
commit 4d1120032a
2 changed files with 11 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+9 -6
View File
@@ -21,14 +21,17 @@ approval asked by a non-approver; no finding is open. M5 (memory, then the sched
M5a, M5b and M5c by P17 to P21 (applied 2026-09-24). M5a (local memory, `memoryd`, spec
`docs/specs/2026-09-24-m5a-local-memory.md`, 22 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 a recalled tainted note left a session trusted, fixed by task 21. Its one open
item, a reason in invalid-arguments refusals, is in `docs/decisions.md` for M5b. P24 split the
rest of M5: M5b is hardening (sanitizer, tag neutralisation, the secret store for every role) and
is next, with no spec yet; M5c is Honcho, through the owner's `roncho` once it has a tagged
release (`docs/specs/2026-09-25-roncho-requirements.md`); M5d is the scheduler. P22 (proposed, not applied) makes Boxmaker a fleet of
check found that a recalled tainted note left a session trusted, fixed by task 21. P24 split the
rest of M5. M5b (hardening: the sanitizer, tag neutralisation in `loopd`, images and untrusted
links as code in `gatewayd`, the invalid-arguments reason, `bxcore::secrets`, one instance per
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
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-m5a` is a clone built with `nix build`. The owner's Honcho
on straylight, where `~/src/boxmaker-m5b` 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,