Go-Live Readiness

What the code has proven vs what only the owner can do

An honest readiness surface. The safety defenses are proven to fire — reproducibly, deterministically, through the same governance code the daily cycle uses. What remains is owner-only: an owner decision, a legal review, custody and an audit. The 30-evidenced-day minimum is met (120/30); only days with a real daily-cycle log count. Live capital still needs an owner decision and a legal review, and the live phase needs custody and an audit. Nothing here moves capital.

Live status

Governance defenses

—

fire on stress (SOFT −5.00% / HARD −10.00%)

Go-live gate

—

— evidenced track-days

Target

—

time-gated, not code

Ready streak

—

consecutive READY days (7 sustained wanted)

Owner-only blockers (code cannot satisfy these)

Reproduce it yourself

python3 scripts/verify_spa.py data/                    # proof chain intact
python3 scripts/defenses_exercised_report.py          # 11/11 defenses fire
python3 -m spa_core.paper_trading.pre_cutover_gate     # 16/16 money-path defenses (inert)
python3 scripts/kill_switch_drill.py                   # emergency-stop latency drill (dated evidence)

Emergency-stop (kill-switch) drill: —

Capital efficiency: —

The code proves the defenses fire; custody / audit / legal / the 30-day evidenced track are owner-only and time-gated.