> 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/platform.md).

# Platform

- [Introduction](https://city-protocol.gitbook.io/docs/platform/introduction.md): What City Protocol is, what it offers and where it stands as of September 2026.
- [The problem](https://city-protocol.gitbook.io/docs/platform/introduction/the-problem.md): Why packaged investing stays gated, and why every onchain issuer rebuilds the same stack.
- [Existing onchain infrastructure](https://city-protocol.gitbook.io/docs/platform/introduction/existing-onchain-infrastructure.md): The assets, settlement, standards and regulation that onchain structured products build on.
- [How City Protocol differs](https://city-protocol.gitbook.io/docs/platform/introduction/how-city-protocol-differs.md): Shared manufacturing for structured products, with two architectures under one layer.
- [Glossary](https://city-protocol.gitbook.io/docs/platform/introduction/glossary.md): Definitions of the terms used across the City Protocol documentation, from the products and their contracts to tokenization, verification and Polis Points.
- [Products](https://city-protocol.gitbook.io/docs/platform/products.md): Curated Vaults and Onchain Token Portfolios, offered to users through Venzo.
- [Curated Vaults](https://city-protocol.gitbook.io/docs/platform/products/curated-vaults.md): Access to institutional yield strategies, run by a named curator inside a mandate that the contracts enforce.
- [Onchain Token Portfolios](https://city-protocol.gitbook.io/docs/platform/products/onchain-token-portfolios.md): A rules-based basket of tokenized equities, bought into the participant's own account in one click.
- [Curated Vaults and OTPs compared](https://city-protocol.gitbook.io/docs/platform/products/curated-vaults-and-otps-compared.md): What a participant holds, who decides the holdings and how each product exits.
- [Venzo](https://city-protocol.gitbook.io/docs/platform/products/venzo.md): Venzo, the flagship application for Curated Vaults and OTPs, screen by screen, from the marketplace to proof of reserves.
- [Product mechanics](https://city-protocol.gitbook.io/docs/platform/product-mechanics.md): How a Curated Vault reaches users through four layers and an OTP through two.
- [How Curated Vaults work](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-curated-vaults-work.md): Contract design, epoch settlement, NAV and bounded strategy execution in a Curated Vault.
- [Vault modules and roles](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-curated-vaults-work/vault-modules-and-roles.md): The contracts behind each Curated Vault, the nine service modules they implement, the roles that operate them and the governance layer above them.
- [Deposits, capital flow and redemption](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-curated-vaults-work/deposits-capital-flow-and-redemption.md): How capital enters a Curated Vault through the policy gate, settles through asynchronous requests and leaves through liquid or epoch-based redemption.
- [NAV, oracle and proof of deployment](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-curated-vaults-work/nav-oracle-and-proof-of-deployment.md): How a Curated Vault strikes its NAV, which checks a NAV report clears before settlement uses it, and how vault state and deployed capital are verified.
- [Mandate, execution and parameters](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-curated-vaults-work/mandate-execution-and-parameters.md): How the curator's mandate bounds strategy execution, how the contracts and venue controls enforce it, and what each vault configures before launch.
- [How OTPs work](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-otps-work.md): The OTP account model, subscription and exit, and how weights and constituent lists change.
- [OTP modules and participants](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-otps-work/otp-modules-and-participants.md): What defines an OTP, how it differs from a pooled vault, the nine modules that run it and the participants who act around it.
- [Portfolio lifecycle](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-otps-work/portfolio-lifecycle.md): The seven stages of an OTP, from the published methodology to exit or retirement, and the flows that buy and sell the basket.
- [List changes and the Rebalancing Executor](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-otps-work/list-changes-and-the-rebalancing-executor.md): What can change an OTP's constituent list, how each change is published, and how the next-phase Rebalancing Executor and Basket Execution Router will apply it.
- [OTP security and risk controls](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-otps-work/otp-security-and-risk-controls.md): Every OTP control and where it acts, what an emergency pause halts, and the principal OTP risks with the controls that address them.
- [Technical overview](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-otps-work/technical-overview.md): How the OTP infrastructure is built: its eight components, how they connect, the portfolios it runs as of September 2026 and what arrives with the next phase.
- [Smart account specification](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-otps-work/technical-overview/smart-account-specification.md): The OTP smart account: its implementation, how its address is derived, the rules that never change, deployment, recovery, off-chain records and value.
- [Permission specification](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-otps-work/technical-overview/permission-specification.md): The two permissions through which the automation signer acts: the Approval and Trade scopes, their rules and limits, what they deny, and how a grant lives and renews.
- [Trade execution specification](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-otps-work/technical-overview/trade-execution-specification.md): How a Buy, Sell or Rebalance request becomes an onchain trade: requests and their states, the reads, each action's plan, price checks, batch submission, deposits and withdrawals.
- [Security model and trust assumptions](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-otps-work/technical-overview/security-model-and-trust-assumptions.md): What the OTP design guarantees, which layer enforces each guarantee, the trust boundary on price, what a holder still trusts, and how the design fails safe.
- [Deployments and verification](https://city-protocol.gitbook.io/docs/platform/product-mechanics/how-otps-work/technical-overview/deployments-and-verification.md): What the OTPs run on as of September 2026: the shared account infrastructure, each chain's settlement token, venue and reference prices, the reviewed registry, and how to verify an account onchain.
- [Issuance & Operation Layer](https://city-protocol.gitbook.io/docs/platform/product-mechanics/issuance-and-operation-layer.md): The product layer that launches and runs Curated Vault products and OTPs through one seven-stage lifecycle.
- [Curated Vault product layer](https://city-protocol.gitbook.io/docs/platform/product-mechanics/issuance-and-operation-layer/curated-vault-product-layer.md): The ten modules, the participants, the lifecycle, product-level NAV and the controls that turn several components into one Curated Vault product.
- [Tokenization and verification](https://city-protocol.gitbook.io/docs/platform/product-mechanics/tokenization-and-verification.md): How Tokenization as a Service turns a yield source into an onchain product, and how the product's value and claims are verified.
- [Tokenization architecture](https://city-protocol.gitbook.io/docs/platform/product-mechanics/tokenization-and-verification/tokenization-architecture.md): The six modules of the tokenization layer, the NAV per token formula and the participants that operate a tokenized product.
- [Tokenization lifecycle](https://city-protocol.gitbook.io/docs/platform/product-mechanics/tokenization-and-verification/tokenization-lifecycle.md): The seven stages that take a tokenized product from onboarding to redemption or wind-down, and the operations and participants that run it in between.
- [Oracle, attestations and API](https://city-protocol.gitbook.io/docs/platform/product-mechanics/tokenization-and-verification/oracle-attestations-and-api.md): How each value update is verified before publication, what pauses when a check fails, the records behind each claim, the operating controls of the tokenization layer and its integration interfaces.
- [Fees](https://city-protocol.gitbook.io/docs/platform/product-mechanics/fees.md): Curated Vault fees, which each curator sets, how fees are paid, and the OTP fee.