Riftmap Blog

I asked platform engineers how they work out who is downstream of a shared change before it ships.

On 26 June 2026, Nx published a post called Announcing Polygraph: A Meta-Harness for Maximum Agent Autonomy.

I parsed the public HCL of four Terraform module estates and bucketed how every module block pins its version.

On 31 March 2026, Zohar Einy, the CEO of Port, published a post with a headline that did the rounds all spring.

Spend a week on call for a platform team and you will meet the same outage twice.

You change one small shared module.

cloudposse/terraform-null-label is a Terraform module that does nothing at runtime.

Three lines were open in three tabs on my screen last week, and all three declared a dependency that crosses a repository boundary.

A pull request to a repository that a hundred others build on should not merge with one approval from a phone.

Three products shipped the same promise this quarter: see the blast radius of your change before you merge.

How to tune Cursor's codebase index for a large monorepo or a multi-repo workspace — and the one question no amount of tuning makes it answer.

Both agents can be handed more than one repository.

Coding agents got cross-repo access this year.

You have a two-line change staged for platform-base.

I scanned two public GitHub organisations and counted every cross-repository edge between them.

Every guide on shared CI tells you how to write a reusable template.

You have got a one-line fix for the hardening role.

Overmind reads your live AWS, GCP and Kubernetes state to tell you whether a Terraform apply is safe.

Every deprecation guide tells you how to signal that a module is going away.

It is three weeks after the goodbye lunch.

You maintain an internal Python package on a private index.

In January 2026, CVE-2026-0861 landed in glibc.

Tribal knowledge is two different things wearing one name.

You maintain a scoped, internal npm package on a private registry.

Short answer: GitLab Orbit is GitLab's organisation-wide knowledge graph — it indexes source code and the SDLC objects GitLab already stores (merge requests, pipelines, deployments, vulnerabilities) into one property graph you can query over MCP, REST, or…

You maintain a shared GitLab CI template.

The "is Backstage worth it" debate is always about cost: how many engineers, how many months, how much it runs per developer.

Short answer: "Backstage alternatives" is really three searches wearing one query, and the right pick depends on which is yours.

In March 2026, someone filed a feature request on GitHub Community that I have thought about more than any product announcement from that month.

The monorepo vs polyrepo argument is old enough that Buildkite was comparing it to the Vim and Emacs wars back in 2024.

It is a Tuesday in late September 2026.

Spend an hour reading the support forums for any of the big coding agents right now and you will notice the same thread, over and over, in slightly different words.

A pattern I keep running into, first as a consultant and lately in places like r/CursorAI: a developer is working in one repo, asks an agent to change something that touches a shared library living in another repo, and the agent confidently writes code ag…

A platform engineer asks two questions on the same morning.

A platform engineer asks two questions on the same morning.

Where the vocabulary moved, what the products shipped against it, and the layer that's still uncovered.

A scan of the kubernetes-sigs organisation, rendered as a graph: 208 repos, 1,128 cross-repo dependencies, and 153 repos that depend on yaml.

Three weeks ago, the Cortex 2026 Engineering in the Age of AI Benchmark put incidents per pull request up 23.5% and change failure rates up roughly 30% since AI adoption accelerated.

In early April, Meta's engineering team published a piece describing how they used a swarm of 50+ specialised AI agents to map tribal knowledge across one of their large data pipelines: four repositories, three languages, 4,100+ files.

Backstage and the developer-portal category solve a real problem.

A scan of the Prometheus organisation, rendered as a graph: 56 repos, 197 cross-repo dependencies, and 25 repos that depend on client_golang.

A practitioner's guide to calculating your team's CFR without a vendor platform — the DORA formula, the SQL, and the AI-assisted vs human-authored split nobody is publishing yet.

The data is in.

You maintain a shared Go module.

You maintain a shared Helm chart.

You maintain a shared GitHub Actions workflow.

I scanned 244 public repositories to find every consumer of one Terraform module. 149 of them declare it.

You maintain a shared base image.

An honest survey of what exists, what each tool actually solves, and where the gap is widest.

It sounds simple: clone every repo, parse the files, build a graph.