🎤The Keynote
The through-line of the series in one sitting: why conversations have never had a standard file format the way documents, images, and spreadsheets do, and what becomes possible once they do.
Last updated
Was this helpful?
The through-line of the series in one sitting: why conversations have never had a standard file format the way documents, images, and spreadsheets do, and what becomes possible once they do.
Thinking in vCon — the keynote, in one sitting. 17:55.
Documents have files. Images have files. Spreadsheets have files. Conversations never got one. A call lives as a recording in one vendor's storage, a transcript in a second system, a summary in a third, and a few notes typed into a CRM by whoever happened to be on the line. Nothing binds those pieces together and nothing certifies that they belong to each other.
The talk argues that this is not a small gap in tooling. It is the reason conversations are hard to govern, hard to audit, and hard to move between systems. Every integration re-derives what the conversation was, and every re-derivation is another chance for the record to drift from what actually happened.
vCon closes that gap by giving a conversation what every other kind of content already has: a defined container. Parties, dialog, recordings, transcripts, analysis, and rights sit together in one signed object that can be handed from system to system without losing its meaning or its provenance.
AI raises the stakes. Models are trained on conversations, agents act on them, and analytics pipelines make decisions from them. When the underlying record has no fixed shape and carries no permissions of its own, basic questions have no reliable answer: who agreed to what, which transcript a summary came from, whether a recording has been altered since it was captured.
A conversation with a standard format is a conversation you can reason about. Consent becomes checkable rather than assumed. Provenance becomes verifiable rather than asserted. And the conversation becomes portable — something the parties to it can actually hold, instead of a byproduct locked inside whatever platform happened to capture it.
Why documents, images, and spreadsheets all got file formats while conversations never did
What a conversation actually contains once you write it down honestly: parties, dialog, recordings, transcripts, analysis, and rights
How signing and provenance turn a scattered pile of artifacts into a record a recipient can check
What changes for governance, compliance, portability, and AI once the container is standard
Last updated
Was this helpful?
Was this helpful?