> 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/deep-dives.md).

# Deep Dives

Lists the longer papers and essays on this site, with what each one argues and how current it is.

Longer pieces on the reasoning behind vCon's privacy and audit design. For field names and normative rules, use the [Field Reference](https://www.conserver.io/vcons/field-reference.md) and the [Extensions](https://www.conserver.io/extensions.md) pages; where one of these pages and a draft disagree, the draft wins.

* [vCon Lifecycle Management using SCITT](https://www.conserver.io/deep-dives/vcon-lifecycle-management-using-scitt.md): whitepaper on keeping the lawful basis in the vCon and lifecycle events in a SCITT log. Revised 2026-10-06 against lifecycle-01 and lawful-basis-02.
* [Privacy-First Conversation Management](https://www.conserver.io/deep-dives/privacy-first-conversation-management.md): paper on why the legal grounds for processing belong inside the vCon and how a pipeline checks them. Updated for lawful-basis-02.
* [vCons and Increasing End User Agency](https://www.conserver.io/deep-dives/vcons-and-increasing-end-user-agency.md): essay, May 2026, on how purpose grants, expiration and SCITT records give people more control, and where they fall short.
* [SCITT: Supply Chain Integrity, Transparency and Trust](https://www.conserver.io/deep-dives/scitt-supply-chain-integrity-transparency-and-trust.md): short reference to SCITT (RFC 9943, RFC 9942) and how vCon systems use it. Current as of 2026-10-06.

The [vCon GitHub repository](https://github.com/vcon-dev/vcon) and the [IETF VCON working group](https://datatracker.ietf.org/group/vcon/about/) hold the primary sources.


---

# 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/deep-dives.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.
