> 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/tokenization-as-a-service/relationship-other-modules.md).

# Relationship Other Modules

### Relationship to VaaS

TaaS and VaaS are separate but connected layers.

TaaS creates the tokenized representation of a yield product. VaaS operates the vault infrastructure that receives deposits, allocates capital, accounts for yield, monitors strategy exposure, and processes redemption.

In some products, the token issued by TaaS represents a share of a VaaS vault. In other products, TaaS may tokenize an external strategy or fund, while VaaS provides a standardized access vault for distribution through City Protocol.

Together, they form City Protocol's capital layer:

```
    A["Yield Source"] --> B["TaaS: Tokenize"]
    B --> C["VaaS: Vault Operations"]
    C --> D["Earn Module"]
    D --> E["Users / Partners"]
```

***

### Relationship to the Earn Module

The Earn Module is the user-facing layer where users discover and access yield.

TaaS sits underneath the Earn Module as tokenization infrastructure. It prepares yield products so they can be listed, compared, subscribed into, monitored, and redeemed through City Neobank or partner applications.

The Earn Module should not need to know every operational detail of a private credit book, trading strategy, or reserve account. It should receive standardized product data, NAV data, eligibility rules, risk labels, and redemption states from the capital layer.


---

# 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/tokenization-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.