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

# Private Strategy Evaluation Flow

> How protected strategy inputs become public evidence without exposing strategy logic.

This flow describes private strategy evaluation, not the public HTTP-only beta
simulation path.

<Callout>
  Private strategy evaluation protects strategy logic during submission and
  evaluation. It does not make final public execution effects invisible.
</Callout>

## Sequence

```mermaid theme={null}
sequenceDiagram
  participant Builder
  participant Contract as Intent contract
  participant Listener as Operator listener
  participant Runtime as Confidential runtime
  participant Sim as Simulation service
  participant Eval as Ranking evaluation
  participant Evidence as Evidence surface

  Builder->>Contract: Submit protected strategy intent
  Contract-->>Listener: Emit lifecycle event with handles
  Listener->>Runtime: Request permitted decrypt/evaluate inputs
  Runtime-->>Listener: Return decoded strategy material
  Listener->>Sim: Run official simulation profile
  Sim->>Eval: Score against fixed rules and benchmarks
  Eval-->>Sim: Return score, gates, report hash data
  Sim-->>Listener: Return evaluation report
  Listener->>Evidence: Persist compact result and artifacts
```

## What is hidden

<AccordionGroup>
  <Accordion title="Protected strategy material">
    The protected surface is strategy input data during submission and
    evaluation: private parameter choices, strategy component composition,
    pre-selection candidate logic, and internal evaluation inputs that would
    leak builder edge.
  </Accordion>

  <Accordion title="Public or shareable outputs">
    Scores, benchmark diagnostics, eligibility status, report hashes, artifact
    references, and final execution effects if a later guarded deployment
    occurs.
  </Accordion>

  <Accordion title="Remaining leakage">
    Timing metadata, submitter or wallet metadata when revealed, market family,
    public catalog shape, final settlement effects, and behavior inferred from
    repeated public execution.
  </Accordion>
</AccordionGroup>

## Trust assumptions

Confidential evaluation still depends on:

* attested compute configuration,
* operator configuration,
* enclave implementation,
* key and permission management,
* side-channel assumptions,
* governance over which artifacts and scores are published.

See [Privacy Model](/trust/privacy-model) for the full trust boundary.