# 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](/start-here/the-problem-when-self-custody-fail.md)

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

[A Real Example](/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](/execution-scenarios/execution-scenarios-introduction.md).
* If you’re looking for **protocol-level mechanics**, you can skip directly to the [detailed documentation](/protocol-mechanics/read-this-first.md).


---

# Agent Instructions: 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:

```
GET https://docs.cryptolegacy.app/start-here/read-this-first.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.