{
  "apiVersion": "v1",
  "passage": {
    "id": "boundary-dependency-graph-cli-invariants-architecture-unchanged-months-2026",
    "text": "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.",
    "speaker": "Vaibhav Gupta",
    "role": "Co-founder and Chief Executive",
    "organization": "Boundary (BoundaryML)",
    "aiVendor": true,
    "work": {
      "title": "Fighting Slop with Slop",
      "type": "talk",
      "date": "2026-07-31",
      "publisher": "AI Engineer (YouTube)",
      "locator": "4:05",
      "url": "https://www.youtube.com/watch?v=AMiyLItEtLA"
    },
    "grade": "B",
    "verification": {
      "status": "verified",
      "reviewedOn": "2026-11-01"
    },
    "topics": [
      "code-review",
      "autonomy-and-oversight",
      "coding-agents"
    ],
    "functions": [
      "engineering"
    ],
    "figures": [],
    "context": "Gupta is describing how the team keeps the BAML code base from drifting when engineers do not review each other's code.",
    "url": "https://the-ai-record.com/passages/boundary-dependency-graph-cli-invariants-architecture-unchanged-months-2026"
  },
  "notice": [
    "Every passage is reproduced word for word from the cited source.",
    "Check the verification status: \"reported\" means not yet confirmed by an independent second reader.",
    "Organizations flagged aiVendor sell AI tooling and have a reason to publish flattering numbers.",
    "An empty result means the archive holds nothing on it, not that nobody has said anything."
  ]
}