You learn four words. Everything else — runs, sessions, workers, candidates, decisions — is detail inside a build: recorded, openable, and never required reading.
A story appears when the planner suggests it and stays on the board until it is delivered or dropped. Health — building, paused, stopped, needs you — is a badge and a sentence on the card, never a different screen to go find.
Upload specifications, notes, transcripts, a PDF from a client. SwarmCoder extracts requirements as objects, each one traceable back to the sentence it came from. You agree the ones that are real; you park the ones that aren't, visibly and reversibly. Nothing about being mid-build closes intake — new requirements, re-analysis and mid-build discoveries land as drafts at any time.
Every build runs the same pipeline — designed once, machine-checked every time, so no run ever improvises the process.
Give a generic agent a task and watch where the expensive tokens go: it rediscovers that it should read the code first, re-derives that a plan might help, reinvents testing — or doesn't. Every run improvises the lifecycle from scratch, and because the process was improvised, there is no artifact to audit afterwards. No place where "the design" lives.
SwarmCoder's lifecycle is code, with invariants a machine checks. Each stage asks its model the one question that stage exists to answer, and the answer lands in a typed object — a Requirement, a Story, a Task — not in prose an agent can misread next time. So the expensive models are only paid for judgment; every run follows the same path, making a defect findable and fixable once; and every decision has a place to live before it is made.
Agentic software development with full traceability — built on ZeroZ4j by Franz Schöning, Principal Enterprise Architect.