ten agents.
the proposal loop is not a monarch. each role has one job: hunt, explain, attack, verify, or stop the change before it reaches live capital.
one agent writing code and shipping it to a live wallet is a bug waiting for an incident. separate roles, each with a specific job, each able to critique the others’ work, make the loop a review board instead of a button.
the point is not that there are ten. the point is that no single agent has the authority to change the engine. every proposal is written by one role, attacked by another, judged by guardian, and verified before it can move forward. the critic roles have no power to write anything on their own.
@orchestrator
coordinatorthe one that decides what the others work on next.
reads every other agent’s output. finds convergence. finds conflict. allocates the next cycle’s focus.
@trader
operatorthe one with a hand on the order flow.
watches the live book. evaluates setups against the current state. manages open positions end-to-end.
@researcher
analystthe one that reads the receipts and tells you what actually happened.
audits the feedback loops. checks that calibration is converging, not thrashing. produces the evidence the other agents act on.
@strategist
plannerthe one that writes the diffs.
looks for what could be better, not what is broken. proposes architectural changes and new capabilities.
@red-team
adversaryvetothe one whose job is to hate what the strategist wrote.
attacks every proposal before it can ship. looks for edge cases, silent failures, exploit paths.
@guardian
safetyvetothe one that can stop everything. and sometimes does.
monitors safety invariants. validates every proposal after red-team. has final veto power before a diff merges.
@builder
implementerthe one with hands on the repo.
applies approved diffs. runs the test suite. deploys. rolls back if the canary diverges.
@calibration
feedbackthe one that keeps the other loops honest.
analyzes loop behavior over rolling windows. detects drift. recommends bounded parameter adjustments.
@introspector
awarenessthe one that writes the memoir while the rest of them fight.
tracks the system’s own state of mind. which commands fired, which agents disagreed, what was learned.
@publisher
voicethe only agent you hear from, and only when it matters.
turns engine intelligence into human-readable language. telegram alerts, weekly theses, reports.
the four-crew is not the engine
if you followed an earlier version of zero, you met the four-crew: skeptic, contrarian, patient, operator. those characters are still here — but their job is not to run the engine. they narrate a single trade, on a live book, for anyone watching. think play-by-play, not decision-making.
the engine is the review system around live capital. the crew is how one trade gets told.