Skip to main content
Write the smallest team shape that holds up in a page: steps in order, a review that fails a step and runs the step that owns the fix again with the findings, and a person who decides at the end. That is an agent pipeline with a review and a person. Without the review it’s a queue; without the person nobody owns what ships. The neighbour term is a software factory, the same shape at a larger scope.

In Obversa

pipeline() runs the steps in order, and the review is a step in it:
examples/feature-team.ts (excerpt)
review is a panel of three that passes on two and names implement as its target, so a failing review runs the implementer again with the findings. The review stage declares that target in acceptsKickbackTo. approve is a person’s question. maxKickbacks caps how often the review can do that; when the budget runs out, the run fails with the last findings instead of looping. The excerpt comes from a scripted test of the workflow shape. Feature delivery uses Claude, Codex and Gemini for the work.

The three parts

Next steps