The conversation is the record
Messages, decisions and linked work share a channel without replacing their source records.
A channel conversation brings discussion and linked work together. Messages, threads and cards help readers understand what happened and where to look next.
Records have boundaries
A message records what its author sent. A card can link to an issue, document, run or another artifact. The linked object’s own record remains relevant. A link in a channel does not grant access to the object it names.
A discussion outside the application does not appear in the channel by itself. Post its outcome when other members need it. An unrecorded huddle has no audio transcript to consult afterwards.
Decisions need confirmation
A pending-decision card records a question that needs a person. Selecting an answer and applying that answer are separate events. The card can report that an answer was not delivered or that the terminal has not confirmed it.
Read the card’s settled result before treating a choice as applied. A later agent response or run result establishes what work followed.
Reading at different levels of detail
Threads hold discussion around one message. Folded rows reduce detail in a busy conversation. Opening the thread or folded row restores the visible context. Search and message links help you return to that context.
Neither folding nor search is a promise of permanent storage. They work with the records you can currently access.