Skip to main content
Search calls it a software factory. What ships is a workflow: named roles, a review that sends work back, a person at the merge. Obversa is that runtime, on the engines you already use. The factory picture is a belt that turns issues into merged pull requests without a person. The teams that make it work do not run a belt. They run a process: one agent writes, another reviews, the work goes back when the review fails, tests run as commands rather than as agent turns, and a person decides at the end. That process is what you write here, as one file.

The file

The file is examples/teams/feature-delivery.ts.
Every stage names its worker and the files it may write. The review role is a seat from another provider. A failed review sends the work back to the stage that owns it, with the findings, up to the retry you set. The last stage is a person.

What a factory search usually wants

Things that catch people out

  • A product factory is the same search with a bigger scope. The answer is the same: a workflow with the reviews and the person written in.
  • An agent pipeline without a return is a queue. The step that sends work back is what makes the review count. See the review loop.
  • The tests are commands. An agent that runs and supervises a test suite burns tokens to do what a command does for free. Write run stages for them.

Where to go

Domain-specific harnesses for the same file read as one job’s harness; the review loop for how a return works.