> For the complete documentation index, see [llms.txt](https://city-protocol.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://city-protocol.gitbook.io/docs/vault-as-a-service/relationship-other-modules.md).

# Relationship Other Modules

### Relationship to TaaS

TaaS tokenizes yield products. VaaS operates the vaults behind them.

In the City Protocol capital layer, TaaS can issue the tokenized representation of a product, while VaaS manages the vault mechanics: deposits, share accounting, strategy allocation, NAV updates, monitoring, and redemption.

**For example:**

```
    A["Asset / Strategy"] --> B["TaaS Product Token"]
    B --> C["VaaS Vault"]
    C --> D["NAV + Verification"]
    D --> E["Earn Module Listing"]
    E --> F["User Deposit / Redemption"]
```

This separation allows City Protocol to support multiple product designs. Some products may be token-first. Others may be vault-first. The infrastructure can support both.

***

### Relationship to the Earn Module

The Earn Module is the user-facing layer.

VaaS sits beneath it as the vault operating system. It provides the smart contracts, accounting, policy controls, monitoring, and redemption logic that allow City Protocol and partner apps to expose yield products in a simplified interface.

The Earn Module can display:

· vault type;

· supported asset;

· expected liquidity;

· risk controls;

· current NAV;

· capacity;

· verification status;

· redemption rules;

· historical performance;

· product status.

The user sees a simple yield product. VaaS handles the technical and operational complexity behind it.


---

# 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:

```
GET https://city-protocol.gitbook.io/docs/vault-as-a-service/relationship-other-modules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.