> 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/vcons/vcon-conveyor-infographic.md).

# The Journey of a vCon

An interactive picture of one vCon's trip through a conserver, for readers who want the whole flow at a glance before reading the details.

This interactive diagram draws one vCon's trip as a conveyor belt. It starts at the communication system and the adapter that builds the vCon, then follows the Redis ingress queue into a chain: the ledger registration, the transcriber link, the analyze, tag and redact links, and a custom link calling your own systems. It ends at the storage links, the vCon MCP server and the AI assistants that read the finished record.

[Day in the Life of a vCon](/conserver/day-in-the-life-of-a-vcon.md) walks the same stations in prose, with the configuration for each one. The rules each station follows are in [Concepts](/conserver/concepts.md).

{% embed url="<https://the-journey-of-a-vcon.netlify.app/>" %}


---

# 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/vcons/vcon-conveyor-infographic.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.