> 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/issuance-and-operation-layer/otp-architecture/security-and-risk-controls.md).

# Security and Risk Controls

The OTP Architecture inherits City Protocol's security framework, adapted to a structure in which the protocol never holds participant assets.

<table><thead><tr><th width="158.3515625">Control</th><th>Function</th></tr></thead><tbody><tr><td>Constituent whitelisting</td><td>Only validated, backed, verifiably priced tokenized assets may enter a portfolio.</td></tr><tr><td>Methodology enforcement</td><td>The executor cannot deviate from published constituents, weights, cadence, or triggers. Changes are published and versioned before taking effect.</td></tr><tr><td>Permission scoping</td><td>Delegated permissions are bounded to specific constituents, venues, and call selectors. They carry no withdrawal authority and cannot move assets out of the participant's account.</td></tr><tr><td>Owner revocability</td><td>The account owner may revoke execution permissions unilaterally and immediately. Revocation halts automation and leaves holdings untouched.</td></tr><tr><td>Execution bounds</td><td>Slippage caps, approved venues and routers, and balance-delta verification after every execution batch.</td></tr><tr><td>Price and status checks</td><td>Rebalancing halts on stale pricing, and status propagation halts it where a constituent is paused, impaired, unbacked, or ineligible.</td></tr><tr><td>Role separation</td><td>Methodology, execution, whitelist management, verification, guardianship, and governance are held by different keys.</td></tr><tr><td>Fee visibility</td><td>The full fee schedule is disclosed before subscription and accrues visibly.</td></tr><tr><td>Emergency pause</td><td>Halts new subscriptions and rebalancing during market, execution, or security anomalies. It does not block participant exit, which requires no action by City Protocol.</td></tr><tr><td>Disclosure versioning</td><td>Methodology, constituent list, weights, and risk disclosures are maintained under version control with published change history.</td></tr><tr><td>Structural look-through</td><td>Transparency is a property of the structure rather than a reporting feature. Holdings sit in the participant's own account and are readable onchain at any time.</td></tr></tbody></table>
