> 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/creator-bound-execution.md).

# Creator-bound execution

Creator-bound execution is a core VaaS design principle.

The vault creator or curator defines the mandate of the vault. The Strategy Manager executes within that mandate, but does not control the base vault logic. This creates separation between product governance and tactical execution.

Creator-bound execution includes three layers.

***

### Mandate and intent layer

The vault defines the intended risk and strategy envelope.

**This may include:**

· allowed assets;

· allowed venues;

· allowed strategies;

· maximum allocation per strategy;

· maximum drawdown threshold;

· leverage limits;

· liquidity requirements;

· minimum collateralization;

· redemption period;

· reporting cadence.

***

### Separation of concerns

The Strategy Manager can make tactical decisions such as which approved venue to use or how to rebalance within the mandate.

The Strategy Manager should not be able to:

· change the vault's accepted assets;

· bypass investor permissions;

· exceed allocation quotas;

· deploy to unapproved venues;

· alter redemption logic;

· change oracle policy;

· remove emergency controls.

***

### Automated circuit breakers

If vault state breaches predefined boundaries, automated controls can pause deposits, withdrawals, allocation, or strategy execution.

Triggers may include:

· NAV deviation beyond policy;

· collateralization below minimum threshold;

· stale oracle data;

· unauthorized strategy debt;

· allocation above quota;

· abnormal withdrawal pressure;

· signer quorum failure;

· suspicious transaction patterns;

· emergency governance action.


---

# 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/creator-bound-execution.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.