Skip to content
Merulan

Chat

Chat keeps a thread's messages, attachments, and sharing choices together while you discuss work.

Chat keeps work conversations in Work & Settings. A thread holds its messages and context so you can return to the same discussion.

Ownership

Chat records a thread's creator, title, messages, attachments, and sharing choices. The creator owns changes to its visibility. Access follows the creator or the members with whom the thread is shared. The Console starts a conversation at /c/new and opens a saved thread at /c/[id]. Use the thread list contract for the supported list read and its Surface.

Lifecycle

Chat threads retain their identity as messages arrive or the title changes. A thread can be private or shared with named members. Making the thread private removes its share records. Sharing changes who can read the conversation. It does not transfer ownership to a recipient. Read the thread's current sharing choice before changing access, especially when several people are using its work context.

Boundaries

Chat is a conversation, not a Task or Workflow Run. A message about an assignment does not create that assignment or move its state. Use a Task when someone must own a result. Use the Run's readback when a conversation refers to execution. Sharing a thread also does not grant access to every Record or other object discussed within it.

Failures

Chat refuses visibility changes from anyone other than the creator. A thread that cannot be read may be absent or outside the caller's access. A concurrent edit can also refuse a change. An empty thread list is not proof that no threads exist: a list read can return empty after a service fault. An attachment list can omit files whose download links could not be created.

Recovery

Chat recovery starts with the saved thread address, Workspace, and signed-in member. Reopen that thread to check access and its current content. Ask the creator to change sharing when access is missing. After a concurrent edit, read the current choices before making another change. Reload attachment readback after a link failure. An omitted download does not prove the stored file was deleted.