> 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/documentation.md).

# Documentation

- [Contracts](https://docs.cryptolegacy.app/documentation/contracts.md): Below is a clear overview of each major CryptoLegacy smart contract: its purpose, inheritance, key methods, events, and external interactions.
- [Contract Functions Reference](https://docs.cryptolegacy.app/documentation/functions-reference.md): Below is a clear overview of each major CryptoLegacy contract function: purpose, inputs, outputs, key logic, events, and external interactions.
- [Contracts Data Structures](https://docs.cryptolegacy.app/documentation/data-structures-reference.md): Below is a clear overview of each major CryptoLegacy contract data structure: purpose, fields, types, relationships, and usage within contracts.
- [Contracts Events](https://docs.cryptolegacy.app/documentation/events-reference.md): This document consolidates all known events from the primary CryptoLegacy contracts, along with their parameters and descriptions.
- [Contracts Errors](https://docs.cryptolegacy.app/documentation/errors-reference.md): This document consolidates all known errors from the CryptoLegacy contracts and libraries, as well as any relevant supporting contracts and libraries.


---

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

```
GET https://docs.cryptolegacy.app/documentation.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.