DDaniel Westgaard·Jun 17Your senior engineer just left. Your bus factor was measuring the wrong thing.A senior leaves and the code stays readable. What walks out is the cross-repo dependency map — and your bus factor, measured from commits, never counted it.14 min read·riftmap.hashnode.dev
DDaniel Westgaard·Jun 14Your senior engineer just gave notice. Most of what they knew was in the repos all along.Your senior just resigned and understood how everything connects. Half of that knowledge was never tribal — it was declared in your manifests the whole time.12 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 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
DDaniel Westgaard·May 12AI coding agents need cross-repo context. The teams running them at scale are already building it themselves.Three teams shipped the same diagnosis in two weeks: AI coding agents need cross-repo context. Two built the dependency graph substrate. One built around it.12 min read·riftmap.hashnode.dev13A
DDaniel Westgaard·May 10Meta needed 50+ AI agents to map their tribal knowledge. The most durable piece of their stack is the part you can build today.Three teams shipped the same diagnosis in two weeks: AI coding agents need cross-repo context.11 min read·riftmap.hashnode.dev
