@@ -4,10 +4,10 @@ This document describes the valid Mysis lifecycle states and the transitions bet
44
55 ## States
66
7-- `idle`: Not running. Set on creation and when a mysis fails 3 nudges; requires a commander message/broadcast to resume.
8-- `running`: Active and eligible for nudges; waiting between loop iterations.
9-- `stopped`: Explicitly stopped by user action.
10-- `errored`: Provider or MCP failures after retries; recorded as `lastError`.
7+- `idle`: Not running, but accepts messages. Messages are stored and processed when started. Set on creation and when a mysis fails 3 nudges; requires a commander message/broadcast or explicit start to resume processing.
8+- `running`: Active and eligible for nudges; waiting between loop iterations. Accepts messages.
9+- `stopped`: Explicitly stopped by user action. Rejects messages until relaunched.
10+- `errored`: Provider or MCP failures after retries; recorded as `lastError`. Rejects messages until relaunched.
1111
1212 ## Activity (not a state)
1313
@@ -56,7 +56,18 @@ stateDiagram-v2
5656 - Triggered after 3 failed nudges with no progress.
5757 - Transitions to `idle` and signals that manual attention is needed.
5858
59+## Message Acceptance
60+
61+Messages can be sent to Myses in `idle` and `running` states:
62+
63+- **`idle`**: Accepts messages. Messages are stored and will be processed when the Mysis is started.
64+- **`running`**: Accepts messages. Messages are processed immediately.
65+- **`stopped`**: Rejects messages with error "mysis stopped - press 'r' to relaunch"
66+- **`errored`**: Rejects messages with error "mysis errored - press 'r' to relaunch"
67+
68+User-initiated stop (`stopped` state) and error conditions (`errored` state) require explicit relaunch before messages can be sent.
69+
5970 ## Notes
6071
6172 - State updates are persisted via `store.UpdateMysisState`.
62-- `running` is the only state that accepts new messages.
73+- Messages are accepted in `idle` and `running` states; rejected in `stopped` and `errored` states.