> For the complete documentation index, see [llms.txt](https://www.conserver.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.conserver.io/thinking-in-vcon.md).

# Thinking in vCon

Thinking in vCon is a short-form video series arguing that conversations should be treated as governed, portable artifacts. This section collects the full episodes, source material, and clips.

**Thinking in vCon** is a video series about one idea: a conversation is a thing you can hold. Not a recording locked in a vendor's platform, not a row in a CRM, but a signed, portable object with its parties, its dialog, its consent, and its analysis all in one place.

Each episode takes a single question (privacy, provenance, the shape of a conversation, identity) and works it from first principles up to something you can act on. The standard is vCon. The point is what it lets you build.

{% hint style="info" %}
New here? Start with [A vCon Primer](/vcons/a-vcon-primer.md) for the written version of the argument, then come back and watch.
{% endhint %}

## Start with the keynote

{% embed url="<https://www.youtube.com/watch?v=MjhpMnvcNds>" %}
Thinking in vCon, the through-line of the series, in one sitting. 17:41.
{% endembed %}

Why conversations have never had a standard file format the way documents, images, and spreadsheets do, and why that gap matters now. Introduces vCon as a single trustworthy object carrying a conversation's recording, transcript, metadata, provenance, and rights.

## Episodes

{% content-ref url="/pages/OGzjYEOSm0yXr8hKLn6V" %}
[The Keynote](/thinking-in-vcon/the-keynote.md)
{% endcontent-ref %}

{% content-ref url="/pages/22LtvBLurByEY1JtUSJ0" %}
[Privacy](/thinking-in-vcon/thinking-in-vcon-privacy.md)
{% endcontent-ref %}

{% content-ref url="/pages/3W1a136YQJwLfLNsDalz" %}
[The Conversational Graph](/thinking-in-vcon/the-conversational-graph.md)
{% endcontent-ref %}

## Clips

Short cuts live on the [conserver channel](https://www.youtube.com/@conserverio) and are cross-posted to LinkedIn and Facebook. They stand alone: one idea, a couple of minutes.

Everything in one place, in series order: the [Thinking in vCon playlist](https://www.youtube.com/playlist?list=PLaxNQ-GrpFLc) on YouTube.

## Related

* [Talks, Articles & Press](/talks-articles-press.md): conference keynotes, IETF sessions, and podcasts
* [Why Conversations Need a File](/vcons/a-vcon-primer.md#why-conversations-need-a-file): the core written argument


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.conserver.io/thinking-in-vcon.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.