> 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/start-here/read-this-first.md).

# Read This First

The following articles explain the problem CryptoLegacy addresses, the solution it provides, and a real-life example — using simple, non-technical language.

[The Problem: When Self-Custody Fail](https://docs.cryptolegacy.app/start-here/the-problem-when-self-custody-fail.md)

[The Solution: How CryptoLegacy Works](https://docs.cryptolegacy.app/start-here/the-solution-how-cryptolegacy-works.md)

[A Real Example](https://docs.cryptolegacy.app/start-here/a-real-example.md)

***

#### Want to go deeper?

* 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).
* If you’re looking for **protocol-level mechanics**, you can skip directly to the [detailed documentation](https://docs.cryptolegacy.app/protocol-mechanics/read-this-first.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/start-here/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.
