Human-in-the-loop by default
By default, every trade memo requires operator approval in a dedicated control UI before any order is transmitted. A tightly bounded autonomous-approval pilot (single-contract size, hard per-order loss cap, small daily order limit, symbol whitelist) now runs in the paper environment under staffed operator monitoring — human approval continues in parallel for everything outside the pilot's bounds.
Operational — paper trading
Limit-only entries
Entry orders must be limit orders — enforced at three independent layers (prompt, data model, execution gateway). Market orders are reserved for exits and protective liquidation.
Operational — paper trading
Operator oversight directive
A live oversight file is read before every proposal cycle. If it says halt, the system halts — a human-writable kill document that outranks every agent.
Operational — paper trading
Kill-switch control
A two-step, armed kill-switch in the operator UI — every activation logged, and exercised in a real, logged operational drill in July 2026. Paired with a capital-protector daemon that monitors positions against loss thresholds.
Operational — paper trading
Zero-quantity firewall
Pre-flight checks in every execution gateway refuse malformed orders — a zero or missing quantity can never reach a broker.
Operational — paper trading
State isolation
Paper and live stacks are fully state-isolated — separate databases, separate credentials. The paper stack is provisioned without live-broker credentials, so it cannot place a live order by design.
Operational — paper trading
Pre-trade margin gate
A pre-trade margin gate in the executor validates every order against deterministic margin math before submission — including refusing naked-short structures outright. Promoted from staged audit to enforcing in the paper environment after a monitored soak.
Operational — paper trading
Exposure & concentration caps
Portfolio-level exposure caps (delta, vega, notional) and per-underlying concentration limits are checked before proposals advance and again at execution; risk-reducing closes are exempt by design. Blocks are enforcing in the paper environment, with every decision written to an audit trail.
Operational — paper trading
Duplicate-trade guard
A deduplication gate fingerprints every candidate at two levels — exact trade and structure — and suppresses repeats before they reach approval. Close and roll intents are never suppressed, so risk-reducing flow always passes.
Operational — paper trading
Broker-truth reconciliation
Fill state is reconciled against broker records on a durable order-identity bridge, with a lifecycle writer that pages the operator on ledger-versus-broker divergence — the system's book is reconciled against the broker's, continuously.
Operational — paper trading
Partial-fill compensation
Spread submissions are watched for naked-leg exposure; detection and paging are operational, with graduated response rungs (probe, cancel-to-flat, residual close) built and staged behind an arming gate.
Alerting operational — actions staged
Daily-loss auto-halt
An automated daily-loss halt monitors broker-reported P&L against dual thresholds (percentage of equity and absolute dollars, worse-of-two) and halts new order submissions on breach — trip-tested in a logged drill before enforcement. The fuller tiered ladder (hedge-only mode through liquidation lock-out) remains a design target.
Operational — paper trading
Strategy promotion gates
Designed control: no strategy reaches production without a signed manifest — code hash, out-of-sample metrics, overfitting probability bound, and a paper-trade attestation window.
Design target