Live Execution & Safety

What Changes the Day the Orders Stop Being Simulated

Section 3 of 5

These systems began as paper engines and have been placing real orders since August 2026. Nearly everything on this page exists because of that transition, and the reason is simple: in a paper system every failure is a reporting failure. In a live one, a dropped confirmation is an untracked position on an exchange, a retry can double a trade that already filled, and a configuration flag flipped for one purpose can silently re-arm something you paused weeks ago.

The engineering response has been to make the dangerous things structurally hard rather than merely documented. Separate switches that must agree. An error type that cannot be mistaken for a safe default. A deployment shape that keeps one market's outage away from another's.

2

independent layers on every kill switch

2

boxes, forced by broker allowlists

3

outcomes a fill check can return

0

price decisions made by the manual console

The Two-Box Console

A discretionary trading surface that runs on a laptop and a phone, served from both live servers at once. The split is not a design preference — each broker only accepts orders from one specific address, so consolidating was never available.

Laptop and phoneone page, over a private network, real TLSOptions Boxserves the identical bundle+ its own order APICrypto Boxserves the identical bundle+ its own order APITwo-layer gateenvironment flag AND a runtimeswitch armed from the pageTwo-layer gateenvironment flag AND a runtimeswitch armed from the pageOptions brokerallowlists this box onlyCrypto exchangeallowlists this box onlyIdentical bundles mean either box can serve the page — a crypto outage never blocks options tradingThe console expresses intent only. Every price decision stays with the execution machinery underneath it.

This is the single most important safety decision in the live system, and it came from noticing a trap rather than from a design document.

The obvious implementation of a manual trading console is to reuse the flag that already permits real orders. That flag, on the crypto side, is shared across every strategy. The crypto strategies' real-capital perimeter had been deliberately paused — so switching that flag on to enable manual trading would have silently re-armed every paused strategy at the same time. A human wanting to place one discretionary trade would have restarted automated trading across four symbols without being told.

The console therefore carries its own gate, which overrides the shared context rather than reading it, and there is a test pinning that behaviour so it cannot be refactored away by someone who notices the apparent duplication and tidies it up.

Both gates are two layers that must agree: an environment flag set on the box, and a runtime switch armed from the interface. The environment flag survives restarts and is the slow, deliberate control; the runtime switch is the fast one you can reach from a phone. Neither alone places an order.

Stated as an invariant: arming the console never touches a strategy, and disarming it never stops one. Those two sentences are the whole safety property, and they were only expressible because the two concerns were kept apart.