> 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/what-is-taas/design-goals.md). # Design Goals TaaS is built around **five design goals.** ### Accessibility Tokenization should make yield products easier to access through City Neobank, partner neofinance platforms, APIs, and SDKs. Users should not need to understand the operational complexity behind the asset to evaluate or participate in the product. ### Verifiability Every tokenized product should expose enough data for users, integrators, and monitoring systems to verify the current product state. This includes NAV reports, reserve data, collateralization levels, third-party attestations, service-provider confirmations, and permission changes where applicable. ### Composability Tokenized products should be designed for downstream integrations. Depending on the asset, jurisdiction, and distribution policy, the issued token may be used in vault catalogs, portfolio products, DeFi integrations, collateral systems, liquidity modules, or partner applications. ### Operational control Tokenization should not remove risk controls. It should make them programmable. TaaS supports access rules, role-based permissions, deviation checks, co-signer systems, pausing logic, and policy-defined subscription and redemption behavior. ### Distribution readiness The product should be usable beyond a single issuer page. TaaS prepares products for multichain distribution, neofinance distribution, and eligible DeFi distribution by combining product metadata, eligibility logic, oracle data, and integration interfaces into one framework. --- # 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://city-protocol.gitbook.io/docs/tokenization-as-a-service/what-is-taas/design-goals.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.