The build loop Shipped
devteam does not only review code — it writes it, one gated increment at a time, against a contract pinned before the work starts.
Run from a driving session, because the loop makes commits and can be interrupted. A bare myteams devteam build prints a pointer rather than pretending to run. build stats and build brief are real CLI commands and work standalone — the first shows the convergence curve, the second selects a lane and emits the coder brief without dispatching anything.
The full mechanism
The iteration shape, the deterministic stop authority, lane selection, and the measured convergence data are all under The Pipeline → When review drives the work → The build loop.
Its lanes are not its review lenses
devteam's 187 review lenses are for reading code. The build loop draws on a separate set of 18 build lanes — the same idea pointed the other way, each carrying imperative build guidance rather than review criteria. They live beside the review specialties in the team data and are counted separately here for exactly that reason.