MooBot Quant Firm Architecture
Operator view: runtime status, autonomous trading mode, Ben 10 department model, and core v2 flow.
Is This Running?
Collecting runtime status.
Loading runtime telemetry...
Ben 10 Departments
The aliens are here. These are the operational departments currently mapped in v2.
Portfolio construction, target weights, and capital allocation.
Research ingestion, paper mapping, and hypothesis lifecycle.
Feature engineering, model scoring, and signal ranking.
Order intent routing, venue adapters, and execution policy.
Pre/post-trade controls, kill-switches, and policy enforcement.
Low-latency market ingest, normalization, and feature pipelines.
Health, replay/recovery, incident automation, and SLO tracking.
Core Operating Flow
1. Observe
`dept_data` ingests market ticks and produces normalized features.
2. Decide
`dept_signals` scores opportunities, then `dept_risk` enforces mandatory pre-trade checks.
3. Execute + Recover
`dept_execution` routes intents; `dept_reliability` monitors replay, drift, and incidents.
MarketTickV1 → FeatureVectorV1 → SignalCandidateV1 → RiskDecisionV1 → ExecutionIntentV1 → ExecutionReportV1 → PnLUpdateV1 → IncidentEventV1