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 sendsBackTo. approve is a person’s question. implement’s refine caps how often
the review can do that; when the rounds run 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, Gemini and Grok for the work.
The three parts
Next steps
- Feature delivery: the same shape on real engines.
- A person decides: how the answer comes back to a paused run.