A business process is really a series of conversations. This episode introduces the conversational graph, linking vCons by shared parties and causality so open loops become visible before they become
The running example is a single hospital discharge, followed end to end.
Seen from a database, a discharge is a status field. It moves from one value to the next and eventually reads complete. Seen from the outside, the discharge is a chain of conversations: the physician and the patient, the nurse and the family, the pharmacy, the follow-up call that was promised and the follow-up call that actually happened. The distinction the episode turns on is that status in a database is not the same as state in a conversation thread. A record can say discharged while the conversation still contains an unresolved promise.
That gap is where expensive failures live. A commitment made out loud and never closed does not surface as a red field on a dashboard, because no dashboard was watching the conversation. The process was real. It simply never existed in a form that anything could inspect.
The proposal is to stop treating each conversation as an isolated artifact. A vCon already carries its parties and can reference other vCons, so individual conversations can be linked into a graph: by shared participants, by subject, and by causality, meaning this call happened because that one did.
Once the graph exists, questions that were previously unanswerable become queries. Which threads have an open loop? Which promise was made and never closed? Where did a thread jump systems and lose its state? Those are things a person can act on, and they are also exactly what an AI agent needs in order to be useful rather than merely fluent. An agent that can see the thread can pick it up, and an agent that cannot will confidently start over.
The line the talk closes on is the whole idea in five words: the conversation is the record.
Concepts — parties, dialog, analysis, and how vCons reference one another
Day In the Life of a vCon — the end-to-end flow through the Conserver
The Journey of a vCon — the same path, as a diagram
MCP Server — how AI assistants query vCon data directly, which is what makes graph questions answerable in practice
Why Conversations Need a File — the written form of the underlying argument
Last updated
Was this helpful?
Was this helpful?