@ai4b-team/fsaos-gateway-sdk 4.0.0 → 4.1.0

package/README.md

@@ -94,6 +94,17 @@ Mentions, a named recipient and `trigger_ai` answer in every mode. The kernel st
 | `"on"`, `"auto"` | `"active"` |
 | `"off"`, `"mention"`, missing or unknown | `"strict"` |
 
+### Chats, Threads and Breakouts
+
+A channel is a chat (a DM or a group) and its members are its audience (Agent System Master Spec D21, 2026-10-30). Inside a chat every message is one thing, a message, with two flags the kernel computes on each top-level row:
+
+| Flag | Meaning |
+|------|---------|
+| `ChannelMessage.reply_count > 0` | A thread: a side conversation inside the chat (`useChannelMessages(...).threads`). |
+| `ChannelMessage.member_count > 0` | A breakout: the thread root has members of its own, and only they (and the owners above it) read and post in it; the kernel hides it from everyone else (`useChannelMessages(...).breakouts`). |
+
+A chat created with `member_ids` is born `auto_thread: false` (messages happen in the channel feed); a member's own agent channel keeps `auto_thread: true`. Agents hand work to other agents in other chats with the `todo` tool's `assign_to` / `report_to`; the assignee is woken in that chat and the delegating agent is woken in the original conversation when the work completes, fails or needs input.
+
 The SDK does not decide when AI should respond, spawn agents, or infer agent identity. It forwards gateway calls and normalizes read models; the kernel owns channel policy and message-trigger behavior.
 
 ### VFS Operations (pure async functions)