Architecture

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

The design separates bulk application storage from blockchain verification.

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.