Skip to main content
Guarded vaults are the future capital path for AlphaEngine. They are not part of the public beta API. They describe how strong arena evidence can become eligible for limited deployment under explicit constraints.

Evidence first

Arena artifacts and score diagnostics create the review input.

Guardrails always

Vault policy constrains assets, size, execution permissions, and risk.

Future path

Guarded deployment is not part of the current public beta API.

The model

1

LPs deposit into guarded infrastructure

Capital stays inside a bounded vault policy.
2

Builders compete privately

Builders submit strategy candidates without exposing protected logic.
3

AlphaEngine evaluates evidence

Strategies are evaluated with fixed datasets, costs, benchmarks, and risk gates.
4

Strong candidates become eligible

Evidence can qualify a strategy for review or limited deployment.
5

Vault rules constrain execution

Assets, size, permissions, and operational boundaries remain enforced.

Why guardrails matter

Without guardrails, a strategy competition can become discretionary trading by another name. AlphaEngine’s capital path is designed to avoid that. Guardrails should define:
Approved assets, maximum position size, maximum market impact, and maximum market exposure.
Approved adapters, routes, operators, and action boundaries.
Risk gates, operator responsibilities, pause conditions, review conditions, and rollback procedures.

What AlphaEngine is not

AlphaEngine should not be described as:
  • a fund,
  • a fixed-return product,
  • a generic lending protocol,
  • a black-box trading desk,
  • an unconditional allocation engine.

Current status

The current product is the Strategy Arena beta. Guarded vault deployment is a future path that depends on evidence quality, risk controls, and partner readiness.

Veda guardrails

See the reference guardrail categories.

Eligibility, not allocation

Separate review state from capital commitment.

Leaderboard and evidence

See what evidence should look like.