Evolutionary Trading Algo

Runtime

Broker-only routing and restricted read models

The May 24 wave pinned live and paper-live execution routing to the active broker, disabled dormant broker lanes unless reactivated in code and docs together, and stabilized the restricted surface around server-side read models. The project identity shifted from futures market seed system to multi-ticker futures Trading OS.

3 referenced systems Names protected by review

Public summary

The May 24 wave pinned live and paper-live execution routing to the active broker, disabled dormant broker lanes unless reactivated in code and docs together, and stabilized the restricted surface around server-side read models. The project identity shifted from futures market seed system to multi-ticker futures Trading OS.

Public record

  • Record type, publication date, and public-safe summary.
  • Aggregate evidence posture and operating boundary.
  • Whether the record belongs to research, runtime, safety, evidence, governance, or architecture.

Protected review

  • System names, market-specific routing, and implementation notes.
  • Protected dashboards, sensitive records, and control actions.
  • Detailed operator decision notes that could expose live decision mechanics.