> 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**](/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](/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cryptolegacy.app/protocol-mechanics/read-this-first.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.