Trading Architecture
DraftStatus: Draft
Version: 0.1.0
Last Updated: 2026-05-16
Owner: Axodus Trading
Purpose
Trading architecture separates research, access, execution, risk, API security, monitoring, reporting, governance, and user education so trading products can be reviewed and operated safely.
Scope
This page describes the high-level architecture for internal strategies, treasury-facing strategies, user-facing strategy products, and CEX API execution tooling.
Architecture Layers
- Strategy research layer: hypothesis, market research, indicators, parameters, backtests, and paper trading.
- Strategy registry layer: metadata, status, risk category, access rules, versioning, and deprecation state.
- Access control layer:
$Neurons, subscriptions, Academy certification, eligibility, strategy tiers, revocation, and pause. - User onboarding layer: disclosures, exchange API guidance, account configuration, strategy settings, and confirmations.
- API security layer: least privilege, withdrawal-disabled guidance, encryption if keys are stored, revocation, and exchange warnings.
- Execution layer: strategy engine, signal generation, order submission, position management, errors, and kill switch.
- Risk layer: drawdown limits, leverage limits, position sizing, liquidation awareness, and anomaly detection.
- Monitoring layer: uptime, execution errors, order status, PnL, drawdown, API health, and incidents.
- Reporting layer: performance, risk, user strategy status, treasury reports, and incidents.
- Governance layer: material strategy policy, treasury approval, access policy, risk limit changes, and accountability.
- ACS/Trinity layer: analysis, summarization, risk review, monitoring support, and adversarial review.
Core Data Objects
Core objects may include Strategy, StrategyVersion, AccessRule, UserStrategyInstance, APIKeyRecord, RiskProfile, PerformanceReport, and IncidentRecord.
Execution Infrastructure
Possible infrastructure components include a strategy engine, signal engine, exchange connector, order manager, position manager, risk engine, configuration manager, monitoring service, reporting service, alerting service, and dashboard.
Hummingbot may be a candidate or planned dependency if implementation confirms it. Do not describe active production integration until verified.
Execution States
Strategy instances may be Not Configured, Configured, Paper Mode, Live, Paused, Error, Risk Locked, or Deprecated.
Pause and Kill Switch
Pause conditions may include drawdown limits, daily loss limits, high API error rate, liquidation risk, abnormal order behavior, strategy logic errors, governance pause, security incident, or user manual pause.
Integration Surfaces
Trading may integrate with exchanges, Hummingbot or connectors if used, Academy, Tokenomics, Governance, Treasury, ACS/Trinity, Business, Marketplace, and Accountability.
Risk Considerations
Architecture must protect against order execution errors, stale data, connector failures, risk engine failure, monitoring gaps, configuration errors, infrastructure outages, and user misunderstanding.