From 76a655062e5a0981531b8dffdafc7cbdd12c4294 Mon Sep 17 00:00:00 2001 From: Kyle Isom Date: Sun, 27 Sep 2026 22:45:50 -0700 Subject: [PATCH] M5c-1 plan: the owner's answers (speaker opt-in; rift probe workspace only) Co-Authored-By: Claude Opus 5.5 (1M context) --- docs/plans/M5c1/README.md | 20 +++++++++----------- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/docs/plans/M5c1/README.md b/docs/plans/M5c1/README.md index 793a9aa..a057d79 100644 --- a/docs/plans/M5c1/README.md +++ b/docs/plans/M5c1/README.md @@ -42,7 +42,7 @@ the question on a new socket; `memoryd` gains a `honcho` module (configuration, | 01 | Wire: `Turn.speaker`, `LogRecord::User.speaker` (optional, absent in old logs), `SessionUpdated.turn`, `SessionState` → `SessionStateReply`; fixtures | bxcore | | 02 | `loopd` logs the speaker on the `User` record and sends the turn number in `SessionUpdated` | loopd | | 03 | `gatewayd` sets the speaker: the Mattermost username when every post of the burst is from one person, else none | gatewayd | -| 04 | `bxctl chat --speaker NAME` | bxctl | +| 04 | `bxctl chat --speaker NAME`, opt-in, no default | bxctl | | 05 | `brokerd` serves `run/memory-broker/state.sock` from its state store; runbook `broker-state-unavailable` | brokerd | | 06 | `memoryd`'s `[honcho]` section and its keys, checked at start; runbook `honcho-config-invalid` | memoryd | | 07 | The ledger, `memory/honcho.jsonl`: its records, append, read-through, and the outbox | memoryd | @@ -57,17 +57,15 @@ the question on a new socket; `memoryd` gains a `honcho` module (configuration, After task 14, the design model runs the M5c-1 device check (spec 13) on straylight, rift and the owner's Mattermost. -## Two points for the owner +## The owner's answers (2026-09-27) -1. **`bxctl chat`'s speaker is a flag, `--speaker NAME`.** The spec says "from its - configuration", but `bxctl` has none; without the flag a `bxctl chat` turn has no speaker and - is not synced, which is the spec's rule for an unknown speaker. -2. **Saved Honcho responses.** The fake server in the tests answers from fixtures. Written from - the OpenAPI document alone they could be wrong in the ways the `roncho` review found (the - evidence fields). The design model would record real responses from rift in task 00, in a - throwaway workspace (`boxmaker-plan-probe`) that it deletes afterwards: creating a workspace, - peers, a session, messages and conclusions, and deleting a conclusion. This writes to your - Honcho; nothing else on rift is touched. +1. **`bxctl chat`'s speaker is opt-in: `--speaker NAME`, with no default.** Console turns are + mostly tests, and Honcho can neither forget them nor be shared without them; a `bxctl chat` turn + without the flag has no speaker and is not synced (spec 4). Task 04. +2. **Saved Honcho responses** for the fake server: the design model records real responses from + rift in task 00, in a throwaway workspace, `boxmaker-plan-probe`, that it creates and deletes. + It touches no other workspace on rift, in any way (not even a read): rift has no keys yet, so + the rule is ours to keep. ## Before hand-over