evolution.
liveproposed changes are treated as suspects. one role writes, another attacks, guardian can veto, and the outcome stays on the record.
tonight
next cycle
next cycle
02:00 · nightly
genesis runs when the book is quietest. one cycle per day.
merged
—
proposals that survived review, attack, and canary
killed
—
didn't survive; logged, reasons preserved
path
proposal review
01digestread trades, rejections, near-misses, and calibration drift.
02proposewrite a bounded change aimed at one failure pattern.
03attacklook for silent failures, bypassed gates, stale data, and bankroll risk.
04decideguardian can veto. approved changes still need verification before production.
feed
recent proposals
connecting
fetching from the genesis journal.
how
the supervised loop
- digest. read last 24 hours of trades, rejections, near-misses, calibration drift, lens competition.
- strategize. an agent proposes a single-file diff aimed at a specific failure pattern.
- verify. run tests and static checks before the proposal can move forward.
- red-team. a different agent looks for edge cases, silent failures, bypassed gates.
- shadow. risky changes run away from live capital before they can affect the book.
- record. the proposal, review, and outcome are kept whether it ships or dies.