Conversations & Comms
Keep communication attached to the work and durable outcomes it creates.
Primitive has direct, group and project chats with replies, mentions, attachments, reactions, unread state and notifications. The target model further normalises messages as units and conversations as durable groupings across threads/sessions.
Instead of talking in one app and doing the work somewhere else, Primitive tries to keep the discussion beside the project, task, decision and agent work it creates.
Comms is not just a chat feature. It is the conversational surface over the work graph. Messages should be able to become tasks, decisions, evidence, context or agent instructions while preserving where they came from. Existing chat capability is implemented; the thread/chat/session/conversation vocabulary is still converging.
Implemented communication
Workspace supports direct, group and project chats with replies, mentions, attachments, reactions, unread state and notifications. Agent outcomes can be written durably into their originating chats.
Target grammar
Message is the atomic communication unit. Threads/sessions organise local interaction. Conversation is the durable grouping that can span those local interaction boundaries when the same subject continues.
Control-plane bridge
The HOLARCHY programme specifies Workspace Inbox as a view over Control inboxes, allowing operational signals, escalation and agent coordination to become visible without inventing a second message substrate.
Where this description comes from
These pointers are the authority behind the status and technical description. If implementation and documentation disagree, the canonical implementation or Control contract wins and this page should be corrected.