Operational Architecture
The rules that govern how Nullpunkt Capital researches, deploys, and operates its systems. Immutable by design. Sovereign in execution.
Core Doctrine
The WORM protocol is the single most important operational principle at Nullpunkt Capital. It governs the entire relationship between the research function and the execution function — and the strict separation between the two.
A strategy is researched, validated, and codified exactly once. Upon deployment, it runs without modification, without exception, and without human override — for as long as it remains statistically valid. Modification of a live strategy is treated as a protocol violation, not a management decision.
This constraint exists for one reason: the moment a human modifies a live system based on recent performance, they have introduced discretion. And discretion is the entry point for every cognitive bias the system was designed to eliminate. Drawdowns feel unbearable. Winning streaks feel unstoppable. Neither perception is a valid reason to change a systematically sound strategy.
WORM is not rigidity. It is the enforcement of pre-committed discipline at the one moment — the heat of live trading — when discipline is hardest to maintain independently.
Execution
Our systems execute without any human input at the point of trade. This is not a temporary aspiration or a work-in-progress state — it is a permanent, non-negotiable architectural constraint.
RULE 01
No Override Mechanism
There is no interface through which a human can override a live trade decision. The execution system does not expose a manual intervention layer. This is an architectural choice, not an access control.
RULE 02
Pre-Committed Risk Envelopes
All risk parameters are defined before a strategy goes live and enforced automatically. Position sizing, maximum loss per session, and drawdown triggers are hardcoded constraints, not soft guidelines.
RULE 03
Circuit Breakers Are Absolute
When a circuit breaker triggers — whether by drawdown, volatility breach, or anomalous market condition — the system halts. Resumption requires a formal review cycle, not a simple restart.
RULE 04
Monitoring Is Not Intervention
Systems are monitored continuously. Monitoring surfaces are read-only. Observing a drawdown, a losing streak, or an unusual position does not confer authority to act. The system's current state is the authorised state.
Lifecycle
A strategy does not touch live capital until it has passed through a rigorous, multi-stage validation pipeline. Each stage is a gate, not a checkpoint — failure at any stage terminates the candidate strategy, it does not delay it.
Discovery
Hypothesis generation from microstructure observation and data analysis
Validation
Statistical significance testing, walk-forward analysis, out-of-sample verification
Stress Test
Behaviour under tail events, liquidity crises, and adversarial market conditions
Paper Run
Controlled simulation in live market conditions with zero capital at risk
Deployment
Live execution with full risk envelope. WORM protocol active. No further modification
Architecture
Each layer of the execution stack is designed with a single mandate: to reduce the time and noise between signal and execution to its irreducible minimum.
Layer 1 — Data
Real-Time Market Data Ingestion
Direct exchange feed connections with normalised, timestamp-corrected tick data. Full order book depth captured at sub-millisecond resolution. No third-party data aggregators in the critical path.
Layer 2 — Signal
Signal Computation Engine
Compiled, hardware-optimised signal calculation running against live order book state. Signals are deterministic — identical inputs always produce identical outputs. No stochastic elements in the signal layer.
Layer 3 — Decision
Rule Evaluation & Order Generation
WORM-governed decision engine evaluates signal state against pre-committed rule set. Order parameters — size, type, limit, time-in-force — are generated entirely by the rule engine without human approval.
Layer 4 — Execution
Low-Latency Order Routing
Co-located order management system with direct exchange connectivity. Kernel-bypass networking, optimised TCP stack, and deterministic order routing to minimise round-trip latency to matching engine.
Layer 5 — Control
Risk & Circuit Breaker Layer
Parallel, independent risk process with write authority to the execution layer. Can halt all activity instantaneously on breach of any pre-defined threshold. Operates on a separate hardware path to guarantee responsiveness under load.