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

# Strategy Submissions

> How builders shape candidates for the Strategy Arena beta.

A strategy submission is a candidate configuration that can be simulated and
evaluated under the arena rules.

<CardGroup cols={3}>
  <Card title="Candidate shape" icon="table">
    Market, timeframe, strategy components, weights, parameters, and caller
    metadata.
  </Card>

  <Card title="Server-owned profile" icon="shield">
    Datasets, execution policy, and scoring windows are fixed in competition
    mode.
  </Card>

  <Card title="Private path" icon="lock">
    Protected submissions can use the encrypted intent runtime, separate from
    public HTTP routes.
  </Card>
</CardGroup>

## What a beta candidate contains

In the public API flow, a candidate is built from:

* `marketId`,
* optional `timeframe`,
* strategy components,
* component weights,
* strategy parameters,
* caller-supplied correlation metadata such as `submissionId`.

The public router owns request validation and route contracts. Strategy math
lives in the strategy package. Simulation orchestration lives in
`simulation-service`. Evaluation lives in `ranking-evaluation`.

## Parameter defaults

Strategy metadata endpoints can expose `defaultValue` for optional parameters.
If a parameter has a surfaced default, callers may omit it and the producer
runtime applies the canonical default.

The router does not invent separate strategy defaults.

## Competition profile

Current public competition mode is server controlled:

<AccordionGroup>
  <Accordion title="Dataset and timeframe">
    Official hourly dataset by default, optional `timeframe = "daily"`, and
    internal dataset resolution by market.
  </Accordion>

  <Accordion title="Scored-window policy">
    Fixed scored-window policy plus fixed execution and scoring profiles.
  </Accordion>

  <Accordion title="Execution knobs">
    Caller-supplied execution knobs are ignored when competition mode owns the
    policy.
  </Accordion>
</AccordionGroup>

This keeps submissions comparable. Builders compete on strategy design, not on
choosing easier evaluation settings.

## Private submission path

AlphaEngine also has an encrypted intent runtime for protected submissions.
That path is separate from the public HTTP API. It uses on-chain intent records,
an internal listener runtime, and confidential evaluation infrastructure.

Use this framing:

<Callout>
  AlphaEngine keeps strategy inputs confidential during submission and evaluation,
  while scores, evidence artifacts, and final effects can become public.
</Callout>

## Submission boundaries

Do not treat a candidate as:

* a promise of capital,
* a live trading mandate,
* a public endpoint for operator runtime behavior,
* a bypass around scoring and eligibility gates.

## Related pages

<CardGroup cols={3}>
  <Card title="How the arena works" icon="table" href="/arena/how-it-works">
    See the full beta loop.
  </Card>

  <Card title="API simulations" icon="chart-line" href="/api/simulations">
    Run candidates against official datasets.
  </Card>

  <Card title="Privacy model" icon="lock" href="/trust/privacy-model">
    Understand what stays protected.
  </Card>
</CardGroup>