Dendro Logic: 454 unattended pull requests in twelve days, no reverts, no human approvals
A solo engineer runs a live legal and claims product with headless agents. Tests are written and frozen before the builder exists, a separate session reviews every change, and the limits he hit at that volume were laptop load and CI budget, not the method.
Source: 454 Pull Requests in Twelve Days
Dendro Logic reports a month of mostly unattended building on a B2B legal and claims platform with paying customers. From September 19 to 30, 454 pull requests merged, an average of 38 a day, with six production releases and no reverts. Commits on main went from 125 in August to 885 in September. From October 1 to 22, another 844 pull requests merged. Over September 19 to October 3, the median pull request was 321 lines, the median time from opened to merged was 0.6 hours, 82% of pull requests touched tests, and none had a human approval.
The author says the person's job moved to product decisions and release sign-off, while the checks were built into the loop. A planner writes the failing tests for each small slice of work before a builder exists. The builder may not edit them, and has to pass a check that they are unchanged. Since October 9, CI rejects a bug fix whose regression test also passes on the old code. The gate is a separate review session that never saw the builder's reasoning. It goes round until nothing of medium severity or above is left, or a finding is accepted with a written reason. One billing change was still drawing high-severity findings in its fifth round and needed a sixth. New features ship behind flags that are off by default. By September 26, about 45 finished features were waiting behind flags for the product owner's sign-off.
Why it matters for code review
The piece argues that steady output is safe when every change leaves its proof behind. End-to-end specs on main grew from 30 on September 1 to 405 on October 22, so each later change has to pass everything earlier ones proved. The author also names the costs of running at this volume. With several builders and test stacks on one laptop, load sat at 100% and preflight checks failed on timeouts unrelated to the change. GitHub Actions hit its budget cap on September 28 and CI stopped until it was raised; by mid-October spend had reached a new $800 cap. He says a person glancing at a 321-line diff late at night is a weaker control than these gates. He keeps human approval of every pull request in the version of the process he wrote for teams.