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

docs: decisions: one toolchain, Rust 1.98.1

Browse Source 
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
kyle
2026-09-28 00:04:38 -07:00
co-authored by Claude Opus 5.5
parent d2e6cfa51f
commit 4e823a76e6
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/decisions.md
+1
View File
@@ -6,6 +6,7 @@ Newest first. A decision that changes `docs/design.md` lands in the same commit
| Date | Decision | Reason | | Date | Decision | Reason |
|---|---|---| |---|---|---|
| 2026-09-28 | One Rust toolchain everywhere: 1.98.1, which titan and talos run, pinned in the flake through `rust-overlay` for the Nix build and the dev shell; `rust-version` rises from 1.95 to 1.98. | Owner's decision, 2026-09-27. Plans are checked on titan and run on straylight or talos; a clippy difference between hosts stopped an M5a task (T34). nixos-26.05's own Rust stays 1.95.0, so the toolchain comes from the overlay rather than a newer nixpkgs, which host configs that follow `nixpkgs` would undo. |
| 2026-09-27 | M5c design (spec `docs/specs/2026-09-27-m5c-honcho.md`, approved): the owner and other people are observed Honcho peers, the agent's peer is not; every trusted memory write is mirrored as a conclusion at once (a `user.md` entry as the owner's, a `memory.md` entry or note as the agent's), and undo deletes it; a turn without complete speaker information is not synced; `memoryd` records each decision and send in an append-only ledger, `memory/honcho.jsonl`, which is also the outbox; `recall` searches the local index, other agents' trusted workspaces and the fleet, never the agent's own workspaces; `ask_memory` asks each named workspace by workspace chat, `minimal` by default; API keys per workspace from `bxcore::secrets`. M5c is planned and run in two halves, the write path first. | Owner's decisions, 2026-09-27, grounded in `roncho` 1.0.0 (checked against its requirements) and Honcho 3.2.0 (source read at `v3.2.0`, and rift's live metrics). | | 2026-09-27 | M5c design (spec `docs/specs/2026-09-27-m5c-honcho.md`, approved): the owner and other people are observed Honcho peers, the agent's peer is not; every trusted memory write is mirrored as a conclusion at once (a `user.md` entry as the owner's, a `memory.md` entry or note as the agent's), and undo deletes it; a turn without complete speaker information is not synced; `memoryd` records each decision and send in an append-only ledger, `memory/honcho.jsonl`, which is also the outbox; `recall` searches the local index, other agents' trusted workspaces and the fleet, never the agent's own workspaces; `ask_memory` asks each named workspace by workspace chat, `minimal` by default; API keys per workspace from `bxcore::secrets`. M5c is planned and run in two halves, the write path first. | Owner's decisions, 2026-09-27, grounded in `roncho` 1.0.0 (checked against its requirements) and Honcho 3.2.0 (source read at `v3.2.0`, and rift's live metrics). |
| 2026-09-27 | M5b settles three open items. An invalid-arguments denial carries its reason (`ToolResponse::Denied.detail`, one line, 300 characters at most). `loopd` neutralises the model's chat-template tags when text from outside is first logged (user messages, tool results after their cap, the memory block), checked against the tokenizer by the self-test in two `/tokenize` requests. The secret store is `bxcore::secrets`, behind the `secrets` feature, for every role but `loopd`. | M5b spec, sections 4, 5 and 8; landed 2026-09-27, device-checked on straylight (review in `docs/implementer-log.md`). The self-test's per-tag requests overran `inferproxy`'s burst on the device and were batched (review finding 10). | | 2026-09-27 | M5b settles three open items. An invalid-arguments denial carries its reason (`ToolResponse::Denied.detail`, one line, 300 characters at most). `loopd` neutralises the model's chat-template tags when text from outside is first logged (user messages, tool results after their cap, the memory block), checked against the tokenizer by the self-test in two `/tokenize` requests. The secret store is `bxcore::secrets`, behind the `secrets` feature, for every role but `loopd`. | M5b spec, sections 4, 5 and 8; landed 2026-09-27, device-checked on straylight (review in `docs/implementer-log.md`). The self-test's per-tag requests overran `inferproxy`'s burst on the device and were batched (review finding 10). |
| 2026-09-27 | The two driver trials of M5b's run, judged: `RESUME` stays, and now also resumes a session stopped at the time limit, the case where it was needed (task 10); `SLOTS_URL` stays, though it never fired. Sessions run with `opencode run --pure` and `OPENCODE_DISABLE_CLAUDE_CODE=1` by default (`PLUGINS=1` restores both), and the prompt names the log row. | The run's evidence (implementer lessons T47, T48): global plugins rewrote the system prompt mid-session and cost 76 of 111 minutes of prompt processing in tasks 01 to 10; task 10 stopped at the limit with its work uncommitted; task 14's row took its name from the heading. `89a50bc`. | | 2026-09-27 | The two driver trials of M5b's run, judged: `RESUME` stays, and now also resumes a session stopped at the time limit, the case where it was needed (task 10); `SLOTS_URL` stays, though it never fired. Sessions run with `opencode run --pure` and `OPENCODE_DISABLE_CLAUDE_CODE=1` by default (`PLUGINS=1` restores both), and the prompt names the log row. | The run's evidence (implementer lessons T47, T48): global plugins rewrote the system prompt mid-session and cost 76 of 111 minutes of prompt processing in tasks 01 to 10; task 10 stopped at the limit with its work uncommitted; task 14's row took its name from the heading. `89a50bc`. |