Block's Builderbot: AI protection agents for system architecture with parallel code review subagents
Block's engineering organization faced degenerative patterns where individual teams ship features that are locally rational but globally corrosive, and no single engineer can hold the full system in their head. Existing AI tools acted as assistants or advisors that waited for humans to act, and agents fumbled around in unfamiliar repositories without consistent entrypoints.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Pre-push hook triggers checks
Local agents run standardized checks via pre-commit and pre-push hooks before code is pushed to a PR.
Builderbot sits between builders and systems as a continuous protector, with pre-push checks shifting validation left, parallel specialized subagents aggregating findings into a single review report, and humans providing only the final stamp of approval rather than initial analysis.
What failed first
Many agentic reviewers were limited to a single prompt expected to cover an entire system, which proved insufficient for hyperlocal context, and CI had become the default validation layer rather than catching issues earlier in the development lifecycle.