> For the complete documentation index, see [llms.txt](https://solari-finance.gitbook.io/solari.finance-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solari-finance.gitbook.io/solari.finance-docs/custody-first-architecture.md). # Custody-First Architecture How the Trust Engine, Operations Layer, and Yield Engine preserve clear boundaries. The strongest digital experience means little if ownership boundaries are weak. Solari therefore begins beneath the interface, with three legally and operationally distinct layers — the Trust Engine, the Operations Layer, and the Yield Engine — each carrying its own responsibilities, assets, records, and risks. The architecture is intended to prevent one layer's obligations from being satisfied with assets belonging to another. ### The Trust Engine Solari intends to use a bankruptcy-remote Delaware Statutory Trust as the Trust Engine — the protected ownership and custody layer for applicable Trust bullion. It establishes the legal, issuance, allocation, custody-boundary, collateral, redemption, evidence, and continuity rules governing eligible gold positions, and it is meant to sit beneath the customer-facing platform rather than behave as another operating business. The trustee, trust administrator, and physical bullion custodian have not yet been named. The applicable trustee, administrator, custodian, governing documentation, and verification framework will be disclosed as part of production activation. ### Ownership is Supported by Distinct Responsibilities Solari connects the client experience to ownership administration, institutional custody, independent verification, and durable continuity — without making any one component the sole source of trust. ![visual-1-solari-system-architecture](https://content.gitbook.com/content/foyvsiE4j1HR210JM2nP/blobs/EQvHdfa0o8EjHYhoV77M/assets/visual-1-solari-system-architecture.svg) The Operations Layer runs the platform itself — accounts, onboarding, product workflows, transactions, and reporting — without ever treating Trust bullion as an asset it can use. The Yield Engine, described later, is elective and touches SUSD only. The Evidence Engine crosses all three without replacing any of them: it organizes supported records, receipts, and cryptographic references, while the legal record, custody record, and transaction record remain authoritative in their own domains. *** --- # 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://solari-finance.gitbook.io/solari.finance-docs/custody-first-architecture.md?ask=&goal= ``` `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.