> For the complete documentation index, see [llms.txt](https://docs.cryptolegacy.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cryptolegacy.app/protocol-mechanics/read-this-first.md).

# Read This First

This section is intentionally **technical and formal**.

It defines **how the CryptoLegacy protocol actually behaves on-chain**, not how it is explained or presented elsewhere.

The goal of this document is to be:

* precise rather than intuitive,
* exhaustive rather than friendly,
* authoritative rather than illustrative.

If you are new to CryptoLegacy, we recommend starting with [**Start Here**](https://docs.cryptolegacy.app/start-here/read-this-first.md).

This section is meant for readers who need exact guarantees, limits, and invariants.

***

Have questions?\
Ask our Custom GPT — [CryptoLegacy AI](https://chatgpt.com/g/g-68c9f2e3d5ec8191a86f75068462c886-cryptolegacy-ai). It explains how the protocol works, without marketing or oversimplification.

If you’re looking for **execution scenarios** that examine CryptoLegacy from multiple perspectives — privacy under pressure, security failures, long-term flexibility, automation without coordination, reliability, legal uncertainty, and cost — go to the [Execution Scenario Articles section](https://docs.cryptolegacy.app/execution-scenarios/execution-scenarios-introduction.md).


---

# 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://docs.cryptolegacy.app/protocol-mechanics/read-this-first.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.
