> For the complete documentation index, see [llms.txt](https://docs.upshift.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.upshift.finance/vault-architecture/atomic-redemption-vault/architecture.md).
# Architecture
The vault sits between the party requesting redemption and the yield strategies that hold the bulk of the capital. An instant-settlement module maintains an immediately accessible reserve, and risk controls bound every settlement.
### **Requestor / Integrator**
The holder or application that submits an atomic redemption request and receives the reference asset in the same transaction.
This is deliberately generic: it can be an end user redeeming directly, a payments integrator settling a transaction, or any contract that needs instant liquidity on demand.
### **Atomic Vault** Contract
The tokenized cash account. It holds the share-pricing logic, converts shares to reference assets against current NAV, and orchestrates the liquidity recall and payout atomically.
### **Yield Strategies**
Curator-managed allocations that hold the majority of vault capital in capital-efficient positions. Capital is deployed automatically when idle and recalled automatically when a redemption needs it.
### **Instant Settlement Module**
A liquidity layer that keeps reserves in highly liquid lending markets (Aave and Morpho) where they can be withdrawn synchronously within the settlement transaction. The module is drawn down to fund settlement and topped back up when surplus liquidity returns.
### **Oracle / Risk Controls**
Price feeds and guardrails (oracle price guards, per-transaction rate limits, redemption fee caps, and spread bounds) that bound every settlement and protect the vault under high-velocity redemption flow.
Refer to this [link](https://etherscan.io/address/0x4eac314be8fec32bfe8f7189040b64e050e801ab#code) for the on-chain implementation contract on Ethereum.
---
# 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://docs.upshift.finance/vault-architecture/atomic-redemption-vault/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.