# Execution Scenarios: Introduction

This section presents a series of execution-scenario articles that examine **CryptoLegacy** from multiple perspectives.

Each chapter explores a specific condition under **owner inability to act** — including privacy under pressure, security failures, long-term flexibility, automation without coordination, reliability, legal uncertainty, and cost. Together, they show how the **same underlying execution model** behaves as real-world assumptions break down.

These are **not separate features or isolated solutions**.\
They are different views of a **single execution system** designed for situations where the owner cannot act on-chain.

Rather than describing what CryptoLegacy *can* do, these articles explain:

* **why the model exists**,
* **which failure cases it addresses**, and
* **how predefined on-chain rules behave** when human coordination, availability, or legal certainty fails.

Taken together, the section forms a coherent narrative about **self-custody beyond key management**  — focused on execution, limits, and continuity over time.

***

#### Want to go deeper?

* If you’re looking for **protocol-level mechanics**, you can skip directly to the [detailed documentation](/protocol-mechanics/read-this-first.md).
* Or ask [**CryptoLegacy AI** ](https://chatgpt.com/g/g-68c9f2e3d5ec8191a86f75068462c886-cryptolegacy-ai)— our custom GPT — to explain how the protocol works, **without marketing or oversimplification**.


---

# 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/execution-scenarios/execution-scenarios-introduction.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.