Skip to main content
You’ve read that a team of coding agents can review its own work and run a step again when the review fails. Before you sign anything in, you want to see that mechanism move: a panel that says no, the writer that runs again, the second attempt that passes. You want it in a minute, on any machine, with no account and no token spent, and you want to be sure the shape you’re looking at is the shape a real team would have. Obversa lets the same file run either way. Every job here is a small function, so the shape is the only thing on show, and swapping a function for an engine doesn’t change the file’s shape. This file is a five-stage team: analyse, implement, test, a review panel of three that passes on two, and a person who decides at the end.

Run it

Set the project up as Installation describes and run the file. It needs no model and no network:
Terminal
Output
implement ran twice. Two of the three reviewers failed the first attempt, so the panel’s findings went to implement, the step that owns the fix, and it ran again. The run didn’t start over. The second attempt passed, and the person at the end said yes.

The file

The writer is a function that leaves the header row out once, so the panel has something to fail:
examples/feature-team.ts (excerpt)
Two of the three reviewers fail the first attempt, because the panel passes on two of three: one dissenting voice is not enough to fail the step, and an example where only one fails would show a panel that passes and prove nothing:
examples/feature-team.ts (excerpt)
The five stages run in order as a pipeline, and maxKickbacks caps how many times a failing panel may run the implementer again:
examples/feature-team.ts (excerpt)
The file ends by checking its own claim: it exits 1 unless implement ran exactly twice and the run passed, so a panel that quietly stopped failing the first attempt would fail the build, not print a passing run.
examples/feature-team.ts

The team’s shape

Next steps