messaginglisted

# messaging — ordinary inbox + explicit wakes Choose delivery before sending: | Mode | Use when | Surface | |---|---|---| | Normal message | Default for every shell-to-shell message. | `sc mem message` | | Wake message | The operator or a loaded workflow explicitly instructs a wake. | The exact wake-producing command named by that instruction/workflow. | Urgency, message kind, or a desire for a prompt response does not authorize a wake. An explicit wake instruction with no supported command -> surface the missing capability and stop. Use only the supported message commands; do not call internal Python or send both modes unless the instruction requires both. ## Normal messages — the shell inbox Normal messages are shell-to-shell markdown driven by `sc mem message`. Sender = you; recipient addressed by `shortname`; body preserved verbatim. The recipient discovers the message on its next boot via the `## STATUS` `Inbox:` count. `sc mem message send` always sends this normal mode; it never wakes or rotates a chat. Trigger: `--message` Args: `check [N] | send <to-shortname> <body> [--kind k] | sent | mark-read <id>` ## Message kinds Every message carries a `kind`, so ordinary mail, delegated tasks, and completion evidence remain independently filterable: - `shell` — ordinary shell-to-shell mail (the default; what `send` does unless told otherwise). - `task` — a bounded instruction for another shell. - `result` — worker → planner completion or transition report. ## chec