> For the complete documentation index, see [llms.txt](https://eni-minds.gitbook.io/eni-minds-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eni-minds.gitbook.io/eni-minds-docs/technical-architecture/extended-explanation.md).

# Extended Explanation

**Layered design ensures modular independence:** Each layer can be **upgraded and extended independently**, reducing system maintenance costs while enhancing ecosystem adaptability.

**On-chain records ensure transparency and trust:** Whether it is task execution or behavior trajectories, all key data are **recorded on-chain**, guaranteeing **transparency and credibility**.

**Cross-chain and modular capability:** The **Ecosystem & Application Layer** can seamlessly integrate **multi-chain, multi-type tasks and third-party modules**, enabling a **global Agent ecosystem**.

**Composable and reusable:** **AINFTs and behavior data** are reusable, providing a **data foundation for long-term task optimization, intelligent strategy upgrades, and incentive mechanisms**.


---

# 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://eni-minds.gitbook.io/eni-minds-docs/technical-architecture/extended-explanation.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.