> ## 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.

# Confidential Compute

> Provider-neutral role of confidential evaluation in AlphaEngine.

AlphaEngine uses confidential compute for sensitive strategy evaluation paths.
It does not require every part of the backend to run inside one private runtime.

## 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:

<Callout>
  Use the weakest sufficient privacy primitive.
</Callout>

## Primitive policy

<AccordionGroup>
  <Accordion title="Trusted execution">
    Use when private computation with attestation is sufficient.
  </Accordion>

  <Accordion title="Fully homomorphic computation">
    Use when encrypted persistent state or encrypted computation materially
    changes the guarantee.
  </Accordion>

  <Accordion title="Zero-knowledge proof">
    Use when external parties need to verify policy or evaluation compliance.
  </Accordion>

  <Accordion title="Threshold cryptography">
    Use when no single runtime or operator should see plaintext.
  </Accordion>

  <Accordion title="Normal access control">
    Use when confidentiality does not change the product outcome.
  </Accordion>
</AccordionGroup>

## 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

<CardGroup cols={3}>
  <Card title="Privacy model" icon="lock" href="/trust/privacy-model">
    What is hidden, what leaks, and what becomes public.
  </Card>

  <Card title="Trust and confidential compute" icon="shield" href="/trust/confidential-compute">
    Operational assumptions behind confidential evaluation.
  </Card>

  <Card title="Private strategy evaluation flow" icon="file-check" href="/architecture/private-strategy-evaluation-flow">
    Follow protected strategy inputs through evaluation.
  </Card>
</CardGroup>