Bots and communication

Account boundaries

Verify bot identity, destination and owner access on the real deployment. This documentation contains no owner-specific bot handles or credentials.

Queued sends must expose actual recipients and message bodies for review. A summary is not sufficient consent.

A group is a workspace, not an authority

A threaded group is a routed workspace: each bot answers in its own topic, and a topic can be named rather than numbered, so the owner never has to remember an id.

A topic is a request, never an authorisation. Every bot in the group can read every other bot's messages, so a brief arriving from the group goes through the same authorisation plane and the same audit line as any other brief. Nothing physical is triggerable from a group, because the interlock holds the wall at the actuator rather than trusting the message.

Receipts

A tool response is not evidence that a recipient read the message. Report available delivery evidence and failures accurately.