> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alphaengine.trade/llms.txt
> Use this file to discover all available pages before exploring further.

# Veda Guardrails

> How Veda-style vault rules constrain any future capital deployment.

Veda-style guardrails are the reference model for future AlphaEngine capital
deployment.

The key idea is simple: capital can follow selected strategies only inside a
bounded vault policy.

<CardGroup cols={3}>
  <Card title="Policy before deployment" icon="shield">
    A strategy cannot bypass vault policy because it ranked well.
  </Card>

  <Card title="Evidence feeds review" icon="file-check">
    Arena evidence informs eligibility and pilot sizing.
  </Card>

  <Card title="Monitoring continues" icon="chart-line">
    Guardrails remain active after selection.
  </Card>
</CardGroup>

## Guardrail categories

| Category              | Example constraints                                     |
| --------------------- | ------------------------------------------------------- |
| Asset allowlist       | only approved markets and tokens                        |
| Size limits           | max notional, max share of vault, max market exposure   |
| Execution permissions | approved adapters, routes, and operators                |
| Risk limits           | drawdown, tail risk, turnover, concentration, liquidity |
| Operational bounds    | pause, review, upgrade, and emergency procedures        |
| Reporting             | artifact hashes, report hashes, final effects           |

## How this connects to the arena

The arena produces evidence. Guardrails decide what that evidence can unlock.

<Steps>
  <Step title="Arena evidence">
    Simulation and evaluation artifacts establish the candidate record.
  </Step>

  <Step title="Eligibility review">
    Review checks evidence quality, gates, and policy fit.
  </Step>

  <Step title="Bounded pilot">
    Any future deployment should be size-limited and policy-constrained.
  </Step>

  <Step title="Continued monitoring">
    Guardrails, reporting, and pause conditions continue after selection.
  </Step>
</Steps>

The strongest candidates should still be limited by the vault policy. A strategy
cannot bypass asset, size, or risk constraints because it ranked well in one
epoch.

## Documentation rule

When describing the capital path, write:

<Callout>
  Evidence creates eligibility. It does not guarantee capital.
</Callout>

Do not imply automatic deployment or fixed returns.

## Related pages

<CardGroup cols={3}>
  <Card title="Guarded vaults" icon="shield" href="/capital/guarded-vaults">
    Future capital path under explicit constraints.
  </Card>

  <Card title="Scoring and benchmarks" icon="chart-line" href="/arena/scoring-and-benchmarks">
    Score evidence that can feed review.
  </Card>

  <Card title="Public settlement" icon="file-check" href="/trust/public-settlement">
    What becomes observable after execution.
  </Card>
</CardGroup>