Skip to content
SAPPHIREENGINEERING PORTFOLIOExplore the architecture
Systems engineering / automated options trading

A trading system
you can inspect.

Sapphire connects market data, strategy decisions, execution and recovery. Explore where state lives, how a trade moves through the system, and what the broker actually recorded.

Take the system tour Inspect the trading record

C++20 · Python handoffs · deterministic lifecycle · SPY options

SAPPHIRE / EXECUTION TOPOLOGY
C++ owns market decisions, option-risk state and router financial authority. Option quotes cross a Python adapter, and selected actions cross Python order dispatch before native admission. Broker evidence returns to the native router.Market & strategyPython quote adapterPython order dispatchOptions & riskNative router authorityIB Gateway / brokerC++ feed and decision stateC++ quote state and exact watchesOrdered events · durable admissionOrders out · broker evidence backC++ feed → typed quote inputSelected action → typed commandC++ ownershipPython on the execution pathOpen the interactive system map Explore
Explicit ownershipNative state, typed boundaries, exact identities.
Durable executionPersist before invocation. Reconcile on recovery.
Inspectable outcomesBroker evidence with operational context.
How it fits together

From a market tick
to a protected position.

The architecture tour moves from the whole system into its native components. Select a component, trace a lifecycle, or switch to presentation mode for a closer look.

01

Market data & decisionsFeed ownership / indicators / ordered strategy state

Filtered ticks, shared features and configured strategy slots produce ordered actions. Python manages configuration and explicit runtime boundaries.

02

Execution & financial truthPython dispatch / native admission / broker evidence

Python dispatches selected actions to native admission. Exact identity and durable intent precede broker invocation; broker evidence updates authoritative exposure.

03

Protection & recoveryRevisioned watches / journals / reconciliation

Protection follows the current quantity. Restart joins durable evidence with broker snapshots; an ambiguous submission is reconciled rather than blindly repeated.

The trading record

Performance, with the
context left in.

A calendar of SPY option executions, monthly realized performance, and documented settings or incidents. Broker evidence and runtime observations are labeled separately.

Open the performance calendar
3,657Broker execution records
14Calendar months shown
94Days with broker activity
4523Distinct recorded context notes

History coverage is partial. Completed-quarter broker records run through 2026-09-30; recent saved captures are shown with explicit gaps. Unmatched SPY activity is not automatically attributed to Sapphire.

Read the evidence standard