The Three Systems
Same Skeleton, Three Very Different Markets
Section 2 of 5
The three systems look alike on a whiteboard and behave nothing alike in practice. Options expire and have strikes. Crypto never closes. Equities trade a fixed session and square off at the end of it. Each of those facts propagates all the way down into the architecture, which is why they are separate projects rather than one engine with a configuration flag.
4
crypto symbols traded independently
2
brokers behind one interface
24/7
crypto — no market-hours gate
1
risk choke point per system
Options Engine — Signal to Ledger
The most involved of the three. Two independent trigger paths converge on one engine, and everything that can open or close a position passes through a single service that owns the risk limits.
Each System in Detail
Options add two dimensions nothing else here has: a strike and an expiry. Every entry therefore involves instrument selection as a distinct step — picking the at-the-money strike against the live underlying and resolving the correct weekly expiry — before any order exists. A signal does not name an instrument; it names an intent, and selection turns that into a tradeable contract.
Two brokers sit behind a shared interface, with one primary and one fallback, wrapped so callers cannot tell which is active. The wrapper deliberately exposes an escape hatch to resolve the underlying client, because broker-specific capabilities exist — one provides websocket streaming the other does not — and code reaching for those would otherwise type-check against the wrapper and silently miss. An abstraction that hides a difference that genuinely matters is worse than one that admits it.
The session has a hard end, which creates its own class of bug. One fix in the history exists specifically because a strategy could open a position after the cut-off at which everything should be flattening — correct in isolation, wrong against the clock.