SSandeep Gautam·Oct 31Your Landing Zone Is Your Governance Model — Design It Wrong and Everything BreaksAccount hierarchy defines blast radius. Identity defines authority. Inheritance enforces control. Everything else is decoration.17 min read·sandeepgautam.cloud2
DDebashish Ghosal·Aug 22From Chatbots to Agentic Workflows (Where the Blast Radius Changes)Only 6% of companies fully trust agents with core processes. How the risk profile changes when AI stops answering questions and starts acting.10 min read·pragmatic-engineer.hashnode.dev
DDr Hernani Costa·Jun 20Why MicroVM Isolation Changes the Blast Radius for Untrusted Agent CodeWhen agents run untrusted code, isolation controls spread. Compare shared-kernel containers, userspace sandboxes, microVMs to limit blast radius.7 min read·radar.firstaimovers.com
DDaniel Westgaard·Jun 15A CVE just hit your base image. Your scanner won't tell you which repos to fix.A scanner finds the vulnerable base image — not the repos you patch. Why base-image CVE remediation is a cross-repo source problem, and how to get the list.11 min read·riftmap.hashnode.dev
DDaniel Westgaard·Jun 12GitLab Orbit maps your whole SDLC. It still can't tell you what an infrastructure change will break.GitLab Orbit is a powerful symbol-and-SDLC graph — but it doesn't parse Terraform, Docker, or Helm. Here's the cross-repo blast-radius layer it can't reach.11 min read·riftmap.hashnode.dev
DDaniel Westgaard·Jun 2The CRA's 24-hour clock is a cross-repo question. Your SBOM answers a different one.The CRA's 24-hour reporting clock asks which products ship an exploited component. Your SBOM lists what is inside one artifact. Those are different questions, and the gap between them is a cross-repo IaC dependency graph.16 min read·riftmap.hashnode.dev
DDaniel Westgaard·May 30Inferred context is not a dependency graphAn enterprise context engine makes your agent generate better code. A parsed dependency graph is the thing you gate a deploy on. Two jobs, two kinds of machinery, and why a confidence score is the wrong guarantee for the second one.16 min read·riftmap.hashnode.dev
DDaniel Westgaard·May 20Cross-repo context is in product docs. The graph is notThe vocabulary moved into vendor docs in sixty days. The parser-derived cross-repo dependency graph it describes hasn't shipped in any AI coding product.17 min read·riftmap.hashnode.dev
DDaniel Westgaard·May 13You don't need a virtual monorepo. You need a graph.Two patterns for AI coding agent context across repos. One scales by hand, one by construction.16 min read·riftmap.hashnode.dev
KKumaran Ravichandran·Apr 19IntroArticles on de-risking changes by discovering impact based on blast radius analysis.1 min read·kumsblogs.hashnode.dev