41,554 blogs · 5,316,985 posts Claim your blog

Record · corpus.blog/posts/01a087d4-d225-7395-a4d7-6e764e9a7c2f

Overmind shows you the blast radius in your running cloud. It can't show you the repos that were building on what you changed.

riftmap.dev · published 19 June 2026

A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.

Read the post at riftmap.dev Wayback capture

0blogs citing

First cited: —
Most recent: —
Rank this month: not ranked
External links: 5
Words captured: 3,146

Cited by

No blog we hold has cited this post yet.

Links from this post

Link

Host

https://overmind.tech/

overmind.tech

https://github.com/overmindtech/cli

github.com

https://docs.overmind.tech/cli/overview

docs.overmind.tech

https://github.com/28mm/blast-radius

github.com

https://overmind.tech/blog/difference-terraform-plan-and-overmind-blast-radius

overmind.tech

Elsewhere on riftmap.dev (8)

GitLab Orbit maps your whole SDLC. It still can't tell you what an infrastructure change will break. Read at the source ↗

https://riftmap.dev/what-is-an-artifact-dependency-graph/

riftmap.dev

How to Find Every Consumer of Your Terraform Module Read at the source ↗

How to Find Every Consumer of Your GitLab CI Template Read at the source ↗

https://riftmap.dev/pricing/

riftmap.dev

https://riftmap.dev/ai-agent-blast-radius/

riftmap.dev

Symbol graphs and artifact graphs: why Sourcegraph stops where infrastructure starts Read at the source ↗

AI coding agents need cross-repo context. The teams running them at scale are already building it themselves. Read at the source ↗