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.
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.
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.
Frequently asked questions
What did this team achieve with this AI workflow?
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 provid…
What tools did this team use?
Builderbot, Just, AGENTS.md, Amp, Agent Skills, sq agents review.
What results were reported?
Burden on human reviewers: reduces the burden on human reviewers; Issue detection speed: faster to catch issues; Local agent effectiveness: massive impacts for our local agents' ability to make the right changes quickly (source-reported, not independently verified).
What failed first in this deployment?
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 e…
How is this quality assurance AI workflow structured?
Pre-push hook triggers checks → Standardized CLI entrypoint → Hyperlocal context loading → Parallel specialized subagent review → Findings aggregated into report → Human final approval → Proactive policy evolution.