MOCKUP — synthetic data

# v0.14 · Paper-Live Soak

Did the runner survive two weeks of IBKR paper trading without manual intervention?

14 days
continuous paper-account run
147 / 143
orders sent / fills (4 rejects)
5 / 5
incidents / auto-recovered

v0.13 hardened the broker plumbing against 11 failure modes (reconnect, idempotency, kill switch, cancel races, clock skew, …). v0.14 ran that hardened runner live against IBKR's paper exchange for 14 trading days with no manual intervention. Five operational events occurred. All auto-recovered.

## Daily equity

Paper account, USD. Period return +3.54%, max drawdown -0.52%. Nothing here is interesting — that's the point.

## What actually happened — incident log

Every operational event during the soak. The system handled all of them without an operator on duty.

When | What | How it recovered
--- | --- | ---
Apr 08 · 09:31 | reconnect TWS API dropped at market open | Auto-reconnect from v0.13 hardening; orders re-queued; 4s delay; no fills lost
Apr 10 · 14:22 | cancel race Cancel sent for order already filled | Fill reconciler caught it; position correctly reflected; no impact
Apr 14 · 11:05 | stale quote Bid > ask on XOM for 2 ticks | Quote validator flagged; orders held 2 ticks; 1 delayed order
Apr 17 · 09:30 | partial+drop 22/38 shares filled then TWS dropped | Reconnect; remaining 16 shares re-sent as new order; correct final state
Apr 22 · 13:41 | clock skew System clock drifted 1.8s vs TWS | NTP resync auto-triggered; audit-log note inserted; no order impact