A team is a file in your repo — diffable, reviewable, pinned by the deploy. The service judges the whole plan before anything runs. N agents writing one shared field lose nothing, and every step settles onto a sealed receipt you can verify.
Agents, shared state, ordering, landings — declared in TOML your reviewers can read in a pull request.
deploy --plan answers with the full refusal catalog and the execution picture — models, orderings, landings — before anything executes.
Concurrent writers compose; contention is counted, not feared. Teams keep memory between runs on a hash-linked chain that follows the team's name.
Zero dependencies. Design partners: install the wheel you were handed — same name, same verbs.
The key names your workspace on tenant-aware services; worlds never touch. An open development service needs no key.
Prefer clicking? The console builds this file for you: declare a team in the browser — same file, same judge.
Validate is the offline gate. --plan is the service's judgment — refusals in plain words, or the picture of exactly what would run. Deploy commits that picture and answers with the deployment id.
The run streams to settlement in your terminal; the console shows the same story — what it was asked, what it produced, where the time went, the receipts and their seals, contention on the shared field. Nothing is lost; everything is on the record.