Skip to main content
AlphaEngine is built for public markets. That means final effects can be public. The privacy goal is to protect strategy inputs and decisioning during submission and evaluation. It is not to make every final market action invisible.

​
The boundary

Private before selection. Public after effects.
This boundary keeps the product honest:

Private before selection

Builders do not have to reveal their edge before evaluation.

Evidence for allocators

Allocators can inspect scores, diagnostics, hashes, and artifacts.

Auditable effects

Final effects remain inspectable after execution.

Risk review

Risk and policy can be reviewed after the fact.

​
What public settlement can reveal

Final effects can reveal:
Asset movement, market impact, and route-level behavior.
Execution timing and cadence can be visible.
Approximate strategy behavior may be inferred over repeated public activity.
This is why documentation must not promise full end-to-end secrecy.

​
Why public effects are useful

Public effects make it possible to audit:
  • whether execution followed approved policy,
  • whether reported outcomes match observable effects,
  • whether guardrails held,
  • whether artifacts describe what happened.

Privacy model

What is hidden and what can leak.

Guarded vaults

Future deployment under explicit guardrails.

Private strategy evaluation flow

Protected inputs before public evidence.