basemind-comms

# basemind-comms — agent coordination over the broker You may be one of several agents working this repo. On start, `inbox_read` and `thread_list` for threads in scope, then skim `thread_history` on the relevant one; `thread_history` / `inbox_read` return front-matter only (subject / from / id) — call `message_get` with an id for a body. Post a concise `thread_post {thread, subject, body, reply_to?}` when you begin, finish, or hit a decision; reply (`reply_to`) to messages about your work; `inbox_ack` clears read messages; don't stay silent when collaborating. This is not optional etiquette: silent agents collide. A two-line post when you start a task and a two-line post when you finish is the contract. ## Identity Your agent id is resolved in this order: `BASEMIND_AGENT_ID` env var → config → persisted agent-id in the machine-global cache → `"anon"`. Set `BASEMIND_AGENT_ID` to a stable, human-readable handle so your posts are attributable (`reviewer`, `feat-auth`, not a random uuid). `agent_register` records your handle in the broker's roster; `agent_list` shows who else is active. ## Threads, scope & explicit join A thread is a scoped conversation addressed by **at least two of three** coordinates — `{subject, path-glob, members}` — so it names a real surface, not a firehose. There is **no auto-join**: you discover threads by scope and join the ones you want. Discovery is always scoped, **never global**. A thread is visible to you when: - **you're a member** — you w...