Trading floor · agent topology
Every agent, every link between them, and when they run — read out of the repository rather than drawn by hand. Click a node to see what it may actually do.
Rhythm
Amber marks the steps an agent performs; the rest is deterministic code that runs whether or not any agent is available. All times UTC.
How to read it
Nothing here is a daemon. An agent is one markdown file. It spawns when invoked, does a task, returns a report, and is gone. No process is sitting there listening.
Links only run downward. A manager spawns a subordinate and gets its report back. There is no peer-to-peer channel and no broadcast — the ringed nodes are the only ones that can spawn anything at all.
The bus is the real nervous system. Anything that must outlive a single agent's life, or cross the Mac/home-PC boundary, is a file in bus/. Being files, it is an audit trail by construction — which for a trading system is worth more than speed.
The watchdog feeds the agents. control/state/incidents/ is literally the work queue: deterministic code writes an incident, an agent picks it up.
ops/build_graph.py — the picture cannot drift from the files.