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.