Conversation as an addressable work surface.
Messages exist because software work is full of explanations, decisions, objections, requests, and handoffs. In many tools, those conversations live outside the project model. They become screenshots, copied notes, or institutional memory. Siloquy treats them as part of the work.
The long-term direction is the same substrate for dispatch and chat. An order can appear as a message to the addressed operator. A reply can become a dispatch record. A discussion can carry references to requirements, assignments, defects, commits, or Meaning Graph evidence. The user sees a conversation; the system still sees traceable project truth.
A conversation becomes trustworthy when it can point back to the work it changed.
This is especially important for agents. Agents should not be tourists arriving from outside the project with a private chat transcript. They should be residents of the workbench, reading and writing through the same Cards, refs, decisions, and evidence that humans inspect later.