Crescendo takes one brief and ships a working product to a live URL a judge can click. Most multi-agent demos stop at a document: a plan, a review, a pull request. Crescendo stops at a running artifact behind a public address, then proves how it got there. Six agents coordinate through Band. The Maestro conducts: it holds the turn and routes every step. The Conductor plans. The Soloist writes the code. The Tuning Fork reviews and catches bugs. Stage Tech deploys. The Archivist keeps memory and the audit trail. The topology is a star: every step goes through the Maestro, so two agents never loop on each other. Each handoff runs through real Band primitives: one shared room, @mention routing, replies read back by sender, and a control loop that sequences them. The deploy is conditional. A deterministic gate headless-renders the page and refuses to ship unless every control works. After the deploy lands, Crescendo fetches the live URL back and hashes the DOM into a per-author signed, hash-chained audit trail. You open the audit report, edit any row, and the chain breaks from there. You verify the tamper-evidence yourself. The orchestra carries memory between runs. The Archivist feeds each agent the skills and fixes it learned on past briefs, so the work compounds. The Band handoff the loop drives is the same unit the audit signs, so what judges look for, agents collaborating through Band, is what the trail records.
Category tags: