> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/developers/autonomys-data-lake/architecture.md).

# Architecture

Understand the trust boundaries in an Auto Drive and XL1 data-lake design.

The design separates bulk application storage from blockchain verification.

```mermaid
sequenceDiagram
    participant User
    participant App as Application service
    participant Drive as Auto Drive adapter
    participant XL1 as XL1 public SDK

    User->>App: Submit bounded payload
    App->>App: Validate schema and canonical bytes
    App->>Drive: Store payload
    App->>Drive: Retrieve by identity
    Drive-->>App: Return untrusted bytes
    App->>App: Revalidate and compare exact bytes
    App->>XL1: Submit approved reference
    App->>XL1: Observe finalized inclusion
    App-->>User: Return separate storage and chain evidence
```

## Trust boundaries

| Boundary               | Responsibility                                                                                                    |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Application            | Authentication, authorization, size limits, schema validation, canonicalization, timeouts, and evidence retention |
| Public storage adapter | Provider connection and payload storage/retrieval                                                                 |
| Auto Drive             | Provider availability and storage behavior                                                                        |
| Public XL1 SDK         | Typed transaction submission and finalized-chain observation                                                      |
| Wallet or signer       | Key custody and explicit approval outside untrusted application input                                             |

## Separate outcomes

Report these states separately:

* **accepted** — the provider accepted a write request;
* **retrievable** — a fresh read returned the exact validated bytes;
* **finalized** — XL1 finalized the intended reference; and
* **archived** — the provider independently reports its long-term archival state.

One state does not prove another.


---

# 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.xyo.network/developers/autonomys-data-lake/architecture.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.