Skip to main content
AlphaEngine is a multi-repo system. The docs should point to module owners instead of inventing a single local workflow.

Replay path

Data capture, simulation, and ranking own the reproducible evidence chain.

Public boundary

api-router owns the public HTTP contract and thin-client route surface.

On-chain boundary

alphaengine-contracts owns intents, vault contracts, and deployments.

​
Core backend flow

1

data-pipeline

Capture deterministic market data and snapshot artifacts.
2

simulation-service

Orchestrate strategy simulation, invariant checks, reports, and artifacts.
3

ranking-evaluation

Score utility, CapitalScore, eligibility, contest logic, and evaluation reports.

​
Module ownership

data-pipeline owns deterministic market capture and snapshot artifacts. simulation-service owns orchestration, invariants, reports, and artifacts. ranking-evaluation owns utility scoring, CapitalScore, eligibility, contest scoring, and reports.
strategies-ts/spot-strategies owns Pendle strategy signals, features, and parameter semantics. amm-math owns deterministic AMM execution adjustment.
api-router owns the public HTTP contract, auth, request validation, and family dispatch.
alphaengine-contracts owns Solidity intent contracts, vault contracts, events, storage, and deployments. listener-service and cofhe own private operator-side infrastructure.
mintlify-docs owns this documentation site.

​
Local commands

Each repo has its own README and agent instructions. Use the module README as the local source of truth. Common backend commands include: 
bun run lint
bun run typecheck
bun run test:fast
bun run ci:pr
Contracts use Foundry: 
forge fmt
forge build
forge test
forge coverage
Docs preview: 
npm install
npm run dev

​
Boundary rules

Public access terminates at api-router. Internal AlphaEngine packages communicate by imports in the MVP.
listener-service and operator-side cofhe are internal infrastructure.
ranking-evaluation must not orchestrate simulation-service in production flow.
ContestScore must stay independent from capital allocation ranking.

System architecture

Public beta flow, encrypted intent flow, and module boundaries.

API overview

Implemented public Strategy Arena routes.

Privacy model

Hidden inputs, public evidence, metadata leakage, and trust assumptions.