Nexus consumes prediction series, validates every proposed trade through a six-stage pipeline, and reserves capital atomically before an order leaves the process. Every state mutation is journaled to a CRC-checked write-ahead log with periodic snapshots, so an instance recovers its exact state after a crash. One Nexus instance manages one trading account.
What Nexus Is Not
Nexus is not:
- a signal generator or model research engine
- a trade execution system or exchange connector
- a market data or backtesting platform
In the wider Vaquum architecture, Origo sits upstream as the data layer and Limen sits upstream as the research engine. Nexus consumes prediction series as Furnace Conduit Arrow frames from any producer — Limen is one such producer, not a dependency. Praxis sits downstream for execution, and Veritas for oversight.
Capabilities
- Six-stage validation pipeline — intake, risk, price, capital, health, and platform limits — with strict ordering and fail-fast denial
- Atomic check-and-reserve capital control guarded by a single lock, closing TOCTOU races between competing strategies
- Per-trade allocation and total utilization caps with per-strategy capital budgets inside one shared pool
- Three operational modes — ACTIVE, REDUCE_ONLY, HALTED — arbitrated by a sole-writer mode controller with sticky manual, risk, and shutdown holds
- Risk circuit breakers for daily loss and drawdown evaluated on the health tick
- Signal intake from Furnace Conduit prediction series in Arrow format, independent of the producer
- Manifest-driven strategy binding with validation of structure, capital arithmetic, and strategy file syntax
- Strategy contract of seven lifecycle hooks covering persistence, startup, signals, outcomes, timers, and shutdown
- Mark-to-market and outcome loops maintaining equity, drawdown, and rolling 24h/7d/30d per-strategy loss windows
- Ordered startup and shutdown sequencing with boot-time capital reconciliation against Praxis that fails closed on divergence
- Durable persistence through a CRC32-checked write-ahead log, atomic snapshots, and crash recovery by snapshot-plus-WAL replay
- Durable outcome deduplication so a crash replay cannot double-apply a trade outcome
First Strategy
The first runnable path is a YAML manifest that binds a strategy file to a Furnace Conduit prediction series, validated through the Python API.
- Install the package from the repository:
pip install "vaquum-nexus @ git+https://github.com/Vaquum/Nexus.git"Nexus requires Python >=3.10 and is not published on PyPI — install it straight from the repository. There are no optional extras; the runtime dependencies are structlog, orjson, msgpack, pyyaml, polars, and numpy. Live signal consumption additionally reads the Conduit serving manifest from /opt/conduit and OHLCV Arrow frames from /opt/arrow (both paths configurable); neither mount is needed for the steps below. Report security issues through the routes in the Vulnerabilities section of this README.
- Fetch the runnable example:
git clone https://github.com/Vaquum/Nexus.gitcd Nexus/examples- Read the manifest — it binds a strategy file to a Conduit series and splits the capital pool:
account_id: example_acctallocated_capital: 10000capital_pool: 10000strategies: - id: logreg_binary_evsfd file: strategies/logreg_binary_evsfd.py signal: series: time_15m interval_seconds: 900 stale_policy: skip name: BTCUSDT 15m up early capital_pct: 100- Read the strategy's decision hook — the loader requires a class named
Strategy, andon_save,on_load,on_startup,on_outcome,on_timer, andon_shutdownare also required abstract methods (this snippet is adapted fromlogreg_binary_evsfd.py):
class Strategy(Strategy): def on_signal( self, signal: Signal, params: StrategyParams, context: StrategyContext, ) -> list[Action]: prediction = signal.get('_preds') if prediction == 1 and not context.positions: return self._enter(signal, context) if prediction == 0 and context.positions: return self._exit(context) return []- Validate the manifest and configure the instance identity:
from decimal import Decimalfrom pathlib import Path from nexus import InstanceConfigfrom nexus.infrastructure.manifest import load_manifest manifest = load_manifest(Path('logreg_binary_evsfd.yaml'))config = InstanceConfig( account_id='example_acct', venue='binance_spot', capital_pct={'logreg_binary_evsfd': Decimal('100')},)Beyond validation, a live instance is wired by a launcher: StartupSequencer recovers state from snapshot and WAL, PredictLoop polls Conduit for predictions, and the Praxis connector routes orders out and trade outcomes back. Nexus runs standalone for strategy development and manifest validation; live order flow requires a Praxis deployment.
Risk Boundary
Nexus is research software. Validation, capital-control, and operational-mode outputs are not investment advice, trading advice, execution simulation, regulatory approval, or a promise of future performance. Past performance is not predictive, and trading digital assets can result in total loss of capital.
Learn more
- Start with the docs tree — Nexus has no published docs site yet
- See the full release narrative in CHANGELOG.md
- Run the complete example in logreg_binary_evsfd.yaml and logreg_binary_evsfd.py
- Read the validation contract in nexus/core/validator
- Follow capital reservation and the order lifecycle in nexus/core/capital_controller
- Trace persistence and recovery through wal.py, snapshot.py, and state_store.py
- See mode arbitration and risk breakers in mode_controller.py
- Inspect the order and outcome flow in nexus/infrastructure/praxis_connector
- Review open debt in TechnicalDebt.md
- Contribute through open issues and the Developer docs
Contributing
Contribution starts through open issues, docs changes, or pull requests against main — Nexus has no dedicated CONTRIBUTING.md yet. Before contributing, start with the Developer docs.
Support
Use GitHub issues for support requests and scope questions — Nexus has no dedicated SUPPORT.md yet.
Vulnerabilities
Report vulnerabilities privately through GitHub Security Advisories. Do not report vulnerabilities through public issues.
Citations
Published work should cite:
Vaquum Nexus [Computer software]. (2026). Retrieved from GitHub.