“This tool basically visualizes our dependency graph internally with some external dependencies as well, … But what's more interesting is we can go build CLI tools that guarantee that certain invariants can't be broken. And what this does is when Claude builds a new package or adds a dependency that's leaky, we now have CI/CD changing or a simple git commit history that tells us exactly where things break. And by this, we're actually able to make our architecture change. We haven't changed our architecture in the last three or four months.”
Vaibhav Gupta, Co-founder and Chief Executive. Runs the company and describes its own engineering practices and the language it builds; Boundary sells AI tooling and has reason to present its approach favorably.
Boundary (BoundaryML) sells AI or agent tooling, so it has a reason to publish flattering numbers about AI. The passage stays in the archive; read it with that in mind.
How this was checked
Checked against the source by a first reader, then confirmed independently by a second reader who fetched the source without seeing the first reader's notes (Independent review agent (Claude Sonnet), blind second pass from passage text and citation only, no repository access, 2026-11-01).
Whisper SRT 00:04:05-00:04:35 matches. Whisper reads 'able to make our architecture change', and the passage reproduces that wording. No captions exist to cross-check it.
How to cite this passage
Vaibhav Gupta (Boundary (BoundaryML)), “Fighting Slop with Slop”, AI Engineer (YouTube), 2026-07-31, at 4:05. https://www.youtube.com/watch?v=AMiyLItEtLA Archived at https://the-ai-record.com/passages/boundary-dependency-graph-cli-invariants-architecture-unchanged-months-2026
Context. Opening of a conference talk by the chief executive of Boundary, the company that builds the BAML programming language, on how its team works.
Boundary (BoundaryML)