Role in AlphaEngine
Confidential compute protects strategy inputs while they are being submitted, decoded, simulated, and evaluated. Public APIs, scoring formulas, artifacts, and final effects remain auditable. Use this rule:Use the weakest sufficient privacy primitive.
Primitive policy
Trusted execution
Trusted execution
Use when private computation with attestation is sufficient.
Fully homomorphic computation
Fully homomorphic computation
Use when encrypted persistent state or encrypted computation materially
changes the guarantee.
Zero-knowledge proof
Zero-knowledge proof
Use when external parties need to verify policy or evaluation compliance.
Threshold cryptography
Threshold cryptography
Use when no single runtime or operator should see plaintext.
Normal access control
Normal access control
Use when confidentiality does not change the product outcome.
What not to claim
Do not claim that public market execution becomes fully hidden. Do not claim that any privacy primitive removes all trust. Do not frame the product as a specific provider integration.What to claim
AlphaEngine keeps strategy inputs confidential during submission and evaluation, while scores, evidence artifacts, eligibility status, and final effects can become public.Related pages
Privacy model
What is hidden, what leaks, and what becomes public.
Trust and confidential compute
Operational assumptions behind confidential evaluation.
Private strategy evaluation flow
Follow protected strategy inputs through evaluation.