Apps have Linux. The cloud has Kubernetes. AI agents have Iterion. Define agent workflows as readable .bot files and operate every run — locally, in CI, or across a multi-tenant cloud.
A .bot is a readable graph. Here's a plan → implement → review loop that keeps fixing until a judge approves — declarative, versioned, re-runnable:
schema verdict:
approved: bool
notes: string
prompt plan_system:
Turn the request into a concrete plan: files, steps, constraints.
prompt implement_system:
Implement the plan, then run the tests.
prompt review_system:
Approve only if the change is complete and the tests pass.
agent plan:
model: "anthropic/claude-sonnet-4-6"
system: plan_system
agent implement:
backend: "claude_code"
system: implement_system
judge review:
model: "anthropic/claude-sonnet-4-6"
output: verdict
system: review_system
workflow ship_it:
entry: plan
plan -> implement
implement -> review
review -> implement when not approved as fix(3)
review -> done when approved… which compiles to this graph and runs it — in parallel where it can, with budgets, sandboxing, and checkpoints:
Design it on the canvas or edit the source — both stay in sync in the visual studio:
Launch from anywhere; the same compiled graph runs the same way — scheduled in parallel, bounded by budgets, isolated in a sandbox, and checkpointed so it can resume:
Iterion ships a maintained fleet of 30+ production bots — real, grounded examples of what an operated agent workflow looks like. A few of the jobs they do:
| Use case | Bots that run it | |
|---|---|---|
| 🚀 | Ship software from a prompt — greenfield apps and end-to-end features | Appy · Featurly · Fini · Bmady |
| 🔁 | Continuously review & improve a codebase — whole-repo and per-branch campaigns, mono-default PR review with optional cross-family confirmation, test coverage | Willy · Billy · Revi · Testy |
| 🏗️ | Modernise a legacy codebase — behaviour-preserving programmes run lot by lot, over a golden-master net that is proved non-blind by mutation, with a doctrine-bound judge for the blocked cases | Morphy · Goldy · Campy · Themis |
| 🛡️ | Automated security & supply chain — SAST, dependency/SCA, diff-scoped CVE & malware shields on every PR | Seki · Depsy · Vulny · Shieldy |
| ⬆️ | Upgrade dependencies safely — multi-stack agentic upgrades with a review gate | Renovacy · Vetty |
| 📚 | Keep docs & knowledge aligned — docs alignment, wiki generation, ADR cartography and ADR re-challenge | Doki · Wikky · Adry · ReArchi |
| ♿ | Accessibility audits — WCAG 2.2 AA / RGAA over deterministic gates | Acci · Ally |
| 🧪 | Close the end-to-end coverage gap — inventory an app's features from the outside, keep a committed feature×coverage matrix, write the missing specs | Endy |
| 📈 | Make a codebase observable — error tracking, standardized structured logs, opt-in tracing | Obsy |
| 🌐 | Stand up a live review environment — deploy the current commit and hand back a real https URL for e2e tests and human review | Envy |
| 🗂️ | Triage & route work — classify board cards, auto-open PRs, answer PR questions | Triagy · Revi |
| 📡 | Watch & react — feed/veille monitoring and digests | Vigie |
| 🧭 | A strategic partner — a conversational co-CTO and roadmap, an architectural visionary | Nexie · Evoly |
Run any bot as-is, fork and adapt one to your repo, or author your own from scratch — in the visual studio builder, with iterion bots create, or by hand in the readable .bot DSL. Package it as a .botz bundle and share it through the marketplace. The same workflow runs unchanged from your laptop to CI to the cloud.
New here? Start with Why Iterion? for the vision, jump straight to Install, or explore the bot fleet.