Skip to main content
Confidential compute reduces strategy leakage during evaluation. It does not remove all trust.

Protect inputs

Evaluate private strategy material inside a restricted runtime.

Publish evidence

Scores, diagnostics, hashes, artifact references, and eligibility can leave the runtime.

Keep assumptions visible

Operator configuration, keys, permissions, and side channels still matter.

​
What confidential compute does

It can let AlphaEngine evaluate private strategy inputs inside a restricted runtime while publishing evidence outside that runtime. That evidence can include:
  • scores,
  • diagnostics,
  • report hashes,
  • artifact references,
  • eligibility output.

​
What it does not do

Confidential compute does not make final public-market effects invisible. It also does not prove that every operator, implementation, or governance choice is correct by itself.

​
Primitive choice

AlphaEngine should choose the weakest sufficient privacy primitive:
Use for private evaluation when attestation is sufficient.

​
Operator assumptions

The current operator-side modules are internal infrastructure. Public builders should not need to operate them to use the beta API. Trust still depends on:
  • runtime configuration,
  • operator permissions,
  • key handling,
  • audited adapter boundaries,
  • typed failure behavior,
  • reproducible artifacts.

Privacy model

The full trust and leakage boundary.

Private strategy evaluation flow

How protected inputs become evidence.

Repo map

Where operator modules live.