The service boundaries, the decision pipeline, the dependency graph between cores and the invariants that hold the whole thing together.
The platform is a monorepo of independent services, each owning its own data, its own documentation and its own deployment unit. Services communicate through files and read-only contracts, not through shared mutable state. There is exactly one writer per dataset.
Service layout
Service
Responsibility
Collector
Continuous acquisition of market data into the single source of truth. The only writer of that tree.
Feeds
Isolated experimental acquisition of candidate sources. Writes to a separate root, never into the source of truth, and computes no derived features.
Core
The live decision engine, its dashboard backend and the paper desks. Reads the data tree read-only.
Research
Offline hypothesis generation, execution and validation against collected history. Never touches live data feeds.
Edge and telemetry
TLS termination, authentication, rate limiting, service health and alerting.
The separation between Collector and Feeds is deliberate. A candidate source with an unstable schema or an unverified provenance must not be able to corrupt the tree that research and the live engine both depend on. Feeds asserts its isolation on every write and refuses to start if its root is nested inside another service's root.
The decision pipeline
The live engine runs a fixed pipeline per cycle:
Data feed – closed bars and aggregates are read from the silver layer, read-only. If the data lag exceeds its bound, every signal in the cycle is marked stale before anything else happens.
Feature store – features are computed once per cycle and memoized by (name, asset, timeframe). An unknown feature name raises rather than returning a default.
Cores – ten decision cores execute in topological order of a lightweight dependency graph.
Resolve – a chain of one-way downgrade rules. Rules may suppress a signal, never promote one.
Post-resolve aggregates – narrative, agreement and a single structured situation object.
Snapshot – a versioned contract written to the dashboard store and served by the API.
Decision journal – every signal of every cycle, including suppressed ones, written to a diagnostic-only branch.
Two cadences drive it: a fast cycle on the five-minute close carrying the cheap cores and the transferred heavy cache, and a heavy cycle on the hourly close that recomputes everything including the committee. A daily maintenance pass settles the journal, runs the degradation monitor, drives the kill engine and evaluates a shadow-null placebo.
The dependency graph
Cores declare what they require and what they produce. The runtime performs a stable topological sort over those declarations at startup. Two properties fall out of this and both are enforced loudly:
A cycle in the graph, or a requirement with no producer, is a startup failure rather than a runtime surprise.
If a required input is missing or not in an OK state, the dependent core is not computed at all. It publishes an abstain carrying the reason missing_dependency – it does not silently substitute a default.
Risk requires volatility and regime. Volatility requires regime. Direction deliberately requires nothing, so that a failure elsewhere cannot manufacture a directional opinion.
The ten cores
Core
Produces
Regime
Current regime, probability of change within the hour, next-state distribution, multi-timeframe coherence
Volatility
Trailing realized volatility, an expansion probability, a quantile forecast band, and a binary risk veto
Structure
Levels, swings, sweeps, compression and liquidity structure
Direction
Committee aggregate, with abstention as the default outcome
Risk
Stop distance as a regime-dependent multiple of ATR, position size, volatility-targeted leverage with an expansion damper
Context
Cross-asset and macro correlation, cross-asset regime coherence
Knowledge
Retrospective hit rates per regime with sample sizes and confidence intervals, plus live forecaster scoring
News
Multilingual sentiment of the news feed with an age guard
Delta
State deltas over 15, 30 and 60 minutes, streaks and a 24-hour memory
Micro
Order-flow sensor over one-minute aggregates
The micro core carries an explicit invariant: it is a sensor describing what is happening now, not a directional predictor. The platform's own audit found no directional edge in order flow, and the core is not allowed to claim one.
Committee aggregation
Where a directional opinion exists at all, it is produced by a committee of trained stacking ensembles rather than by a single model, and the aggregation across committee members is deterministic. There is no learning in the live path. The aggregation applies, in order: a freshness filter on member signatures, a monotone probability calibration map per committee, reliability weights with a maturity guard so that an immature member cannot dominate, a reliability-weighted median across calibrated probabilities, a quorum requirement, and a disagreement threshold.
The median rather than the mean is the load-bearing choice: one broken member moves a mean and does not move a median.
Invariants
These hold across the whole platform and each of them was written after an incident, not before:
No online learning. Nothing refits in the live path. Calibration maps are trained offline, applied statically, and monitored for drift as a one-way degradation signal.
One-way gates. Every resolve rule can only downgrade a signal. No rule can raise confidence or restore a suppressed direction except the explicit volatility recheck, which is symmetric by design and logs both directions.
Fail loud, not quiet. An unknown model architecture, an unknown feature, a non-monotone calibration map or a broken dependency graph raises an exception. Silent fallback to a default is treated as a defect class of its own.
The decision journal is diagnostic-only. The live path never reads it, so no feedback loop can form. A journal failure raises an alert and does not stop the cycle.
Binary composition admission. If any active member of a live composition breaks its registered out-of-sample interval, the whole composition falls back or freezes. There is no re-weighting, no threshold tuning and no partial degradation in production. Recovery is offline re-validation only.
Manual state-write failsafe. If the reliability engine cannot persist its state, it freezes the composition, writes a marker that survives a restart, and requires an operator to clear it.