> For the complete documentation index, see [llms.txt](https://docs.usd.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usd.ai/depositor/marketing-and-summary-disclosures.md). # Marketing and Summary Disclosures sUSDai is a noncustodial, rules-based vault token whose NAV reflects reserve assets and protocol-recognized Depositor NFTs. Ordinary-course borrower payments are routed according to predefined smart-contract logic and applicable loan documents. Neither the Foundation, GPU Finance, Permian Labs, nor any multisig or execution role has discretion to select individual users for redemption, redirect ordinary-course payments, alter yield allocation, or admit loans outside applicable protocol-approved criteria. Authorized roles are limited to implementing disclosed protocol functions, submitting security-controlled transactions, and enforcing objective rights under loan documents following defined events of default. Yield is not guaranteed and depends on borrower payment performance, reserve yield, fees, redemption timing, and applicable default or impairment treatment. --- # 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.usd.ai/depositor/marketing-and-summary-disclosures.md?ask=&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.