The Development Loop: Design, Build, Check, Review
The Development Loop: Design, Build, Check, Review
How one change goes around the development loop: the design and the spec are written before the code, helper agents build, automatic checks run and send failures back, a person reviews and merges, and whoever reported a problem is told only once the new version is running. The review is the one step that never runs without a person.
Every change to the software goes around the same loop. It starts with a request: a person asks for something, or a report from one of the other two loops needs a fix.
Design first. Before any code is written, the agent writes the design down: what will change, which rules the change must keep, and how it will be checked. Where a part of the software has a spec, a numbered list of what must be true, the change updates that list too. For larger work, the plan is approved before building starts, by a person or by a second agent that reviews it. If a design would bend one of the project's standing rules, the agent must stop and ask a person.
Then build. The agent that wrote the design hands the building to helper agents, each working on its own part of the code.
Then check. The agent runs the checks of every part it changed. When it hands the change in, our own servers run the full set. A failure goes back to the agent, which fixes it and tries again. How these checks work is the subject of How We Know It Works.
Then a person reviews. The agent hands in the change with a description of what it did and why. A person reads it, then merges it or sends it back. Only a merged change is published. And whoever reported a problem is told it is fixed only once the new version is running where they use it. The figure follows one change through these hand-offs.