What the record proves.
And where it stops.
Financial values come from broker execution records. Runtime logs explain the surrounding system state. The two are joined only where exact identities support the connection.
Completed-quarter IBKR execution history is available through 2026-09-30. Recent IBKR history requests failed. Selected saved broker executions and preserved runtime notes are included, but recent months are incomplete. Unmatched activity is not automatically attributed to Sapphire.
2025-10-01 → 2025-12-31
2026-01-01 → 2026-03-31
2026-04-01 → 2026-06-30
2026-07-01 → 2026-09-30
2026-10-01 → 2026-11-07
SPY options only. SQQQ, equities, futures and other underlyings are excluded before publication.
Dates and calendar buckets use America/New_York, including daylight-saving changes.
An execution fill is not a round-trip trade. Partial fills are retained; overlapping captures are deduplicated by exact execution ID. Conflicting financial records stop the build.
Connector order-ID discrepancies are retained in the private audit as unresolved metadata. They are never used to join executions or to claim broker order identity; contract and account identity conflicts still stop publication.
Realized P&L is the broker-reported value, attributed to its execution date. It is not cash flow, account return, unrealized P&L or a simulated result. Broker-reported realization already reflects allocated fees; commissions are not deducted again.
A missing realization is unknown, not zero. Selected recent broker captures do not certify complete daily or monthly history. Complete-quarter no-activity months can show zero.
Router logs supply context and exact contract/strategy matches only. Compatibility order_filled rows may be cumulative or have invalid prices; they do not create financial executions in this portfolio.
Overrides describe recorded policy changes or commands. A requested command does not prove application or execution. Day-level incident context is not a claim that an incident caused a particular trade.
SPY charts prefer recorded router market bars. Dates without retained router charts may use explicitly labeled 5-minute OHLCV aggregated offline from recorded historical SPY trades. These reconstructed price series do not establish live-router observations or strategy bands; empty intervals remain absent.
Reconstructed Bollinger bands require retained router closes and same-session exact-route effective parameters; their availability time is distinct from the bucket start. Entry/exit markers use broker execution timestamps; marker height is not an option execution price. Later middle-band conditions do not establish executable option fills.
Raw broker/account/order/execution identifiers, private logs, filesystem paths and credentials are excluded from the public artifact.
Architecture is a source map.
The interactive tour describes inspected source components and their responsibilities. It does not assert that every optional feature is enabled, that the current checkout is deployed, or that a service is presently running. Sapphire Control and research coordinate the system; neither replaces broker evidence as financial truth.
Snapshot collected November 7, 2026 at 11:10 PM Eastern.