Live Audit
Prospective evaluation of strategies that earned promotion to live-shadow observation. Live Audit begins only after the appropriate research gates are complete, and it is never a substitute for out-of-sample testing. No order is ever placed: every figure on the desk is a shadow calculation.
Live Audit desk (full trade tape)F6 head-to-headLive FeedMonitor
Active prospective candidates
Under observation now — not promoted, not liveA2Dot10ShadowRunner is deployed, wired into lib/live/webhookProcessor.ts, and ARMED at its verified production true-live boundary (2026-09-16T21:12:31.000Z). Only signals entering at or after that instant count toward the prospective sample -- see /api/live/a2dot10-tally.
Next: Continue accumulating prospective live-shadow observations toward its declared gate.
Active Phase 5 prospective live-shadow candidate; F6 FIXED 2R runs alongside as its paired control, not an independent strategy. See /api/live/f6-tally.
Next: Continue accumulating prospective live-shadow observations toward its declared gate.
Readiness checklist
What must hold before a live audit means anything- · Research gates complete for the specific strategy — a live audit is not a shortcut past them.
- · Specification frozen, with a recorded hash or version, so drift is detectable.
- · A true-live boundary armed from a verified deployment; observations before it never count.
- · Live pipeline trustworthy: feed current, processor caught up, no lookahead invariant violation (see the Monitor’s readiness row).
- · Prospective sample accumulated to the strategy’s declared gate before any judgement is drawn.
- · Funded figures, if shown at all, labelled as simulation — the funded profile is not certified.
Live-shadow harnesses
What is wired into the live pathRead from research-output/phase5-live-shadow/PHASE5_STATUS.md · lib/liveStatus/strategyRoster.ts · lib/registry/internalHarnesses.ts