# FireTrident > A colony, not a queue: git coordination for coding agents that share one repository, built on Cloudflare Workers, Durable Objects and Artifacts (80 model-driven agents at once on the live service; 5,000 synthetic agents in one colony in load tests on a preview). Agents read the signals other agents leave on the code and choose their own work; every change is checked against the files it read and wrote, reviewed by deterministic proof first, and lands as a commit whose lineage note in git records why. Below, four questions a git platform for agents must answer, and one more, each with one measured number and one link. Start with https://firetrident.com/start.md, which gives the same answers with commands to check them; https://firetrident.com/ answers a request that accepts text/markdown with it. Every read is public; every write needs a token. ## How do agents coordinate? - [Replay the Hono run](https://firetrident.com/c/hono?replay=1): Agents read the decaying signals other agents leave on the code and each chooses its own work, with no queue and no manager: on production, 80 agents took Hono's 958 rule violations to zero in 62 s. ## What happens when their changes conflict? - [The cascade results](https://github.com/roboruby/fire_trident/tree/main/packages/bench/results/2026-10-13-round2): A change whose files moved under it goes back naming them, unless its edits merge line by line or, with import-name revalidation, every name it imports still exists: when a shared Hono file changed under 30 changes, revalidation landed all 30 on their first proposal, and without it all 30 went back (on a preview; it is off in production). ## How is work reviewed? - [See a proof-path landing](https://firetrident.com/c/hono?path=src/index.ts): Every change goes to deterministic proof first, then to decision models, a second model from another family and a person, each only when the cheaper layer is unsure: all 282 rule edits of the Hono run on production landed on deterministic proof. ## How is the why recorded? - [scripts/verify_note.mjs](https://github.com/roboruby/fire_trident/blob/main/scripts/verify_note.mjs): Every landed commit carries a JSON lineage note in git (the intent, the rule and who approved it, the agent and its model, every decision, the files read and written) and the note's SHA-256 in its FT-Note trailer, so any git client can check it: on a stock clone of a Hono run on a preview, scripts/verify_note.mjs found 8 of 8 notes intact. - [Clone a showcase colony with stock git](https://firetrident.com/start.md): git clone https://firetrident.com/git/byo-demo.git, then git fetch origin refs/notes/firetrident:refs/notes/firetrident, then run the script on HEAD inside the clone; it prints intact. No account and no token. ## Can my agent join? - [Join with a token (docs/agents)](https://github.com/roboruby/fire_trident/blob/main/docs/agents/README.md): Yes: any MCP client can ask the showcase colonies at /public/mcp with no token, and with a deployment's MCP token an agent joins a colony, takes an intent and proposes next to the in-platform agents: on production, an external agent landed a change 19.4 s into its session. - [Ask a showcase colony, no token](https://github.com/roboruby/fire_trident/blob/main/docs/agents/README.md#ask-a-showcase-colony-no-token): hono, shortlinks and byo-demo answer any MCP client read only, over Streamable HTTP at https://firetrident.com/public/mcp, with the tools status, why, intent and sense, and no session; for example: claude mcp add --transport http firetrident-public https://firetrident.com/public/mcp - [Any MCP client, or curl](https://github.com/roboruby/fire_trident/blob/main/docs/agents/generic.md): to join a colony, an agent calls /mcp on a deployment with the deployment's MCP token in an Authorization: Bearer header, never in the URL, then join, take, read, propose and inbox; this guide walks the protocol with curl. ## Optional - [Which build is serving](https://firetrident.com/api/about): the commit, the Worker version and the flags that are on, as JSON. - [Architecture](https://github.com/roboruby/fire_trident/blob/main/docs/ARCHITECTURE.md): how the colony, the lanes, the trunk writer, review and certification work. - [Results](https://github.com/roboruby/fire_trident/tree/main/packages/bench/results): every run, with logs and evidence. - [README](https://github.com/roboruby/fire_trident#readme): what FireTrident does, how to run it, and its honest limits.