AI Safety's Vocabulary Problem: The Same Words Mean Different Things to Different People

When drone strikes hit AWS infrastructure in the UAE and Claude went offline hours later on the other side of the world, the observation that surfaced this wasn't from a safety lab or an arXiv preprint. It was a Bluesky post. That the most structurally important safety question in recent weeks — what happens when the physical substrate of AI simply stops existing — got flagged by a casual social media observation rather than a formal risk framework says something uncomfortable about where the field is actually paying attention.

The formal alignment community has spent years building elaborate threat models for AI that gets too capable, too deceptive, or too misaligned with human values. Those frameworks have almost nothing to say about a data center going dark because a building burns down or a conflict zone expands. The Bluesky post framed this explicitly as a gap in risk analysis, and the observation held up under scrutiny from the people who engage with it. Whether the alignment community will treat infrastructure fragility as a legitimate safety concern or quietly file it under "operations" will be a revealing test of how elastic the field's actual definition of safety is.

The technical end of the conversation has moved into a quieter, more methodological phase that produces less external signal but arguably more real progress. The current preoccupation is mechanism-level work: shutdown safety valves that give AI systems an objective to self-terminate if capability thresholds are crossed, participatory evaluation frameworks that researchers are openly revising in public. One researcher noted their thinking on participatory evals had "evolved significantly" in recent months — which is a normal thing for researchers to say, but unusual to say publicly, and suggests a community genuinely mid-revision rather than defending settled positions. This is the least legible version of the conversation to outsiders, and probably the most productive.

Against that backdrop, the Future of Life Institute's pushback on "superintelligent AI will cure cancer" promises reads as a defensive maneuver more than a theoretical advance. The grand existential framing that once defined the field has given way to arguments about what "taking AI risk seriously" means in practice — who evaluates it, by what method, accountable to whom. That's a real maturation, but it comes at a cost: the conversation has become nearly impossible to follow from outside a small number of specialized communities, which may be why volume is up sharply without producing anything resembling a coherent public argument.

What fills the gap is friction. On Reddit, posts labeled "AI safety" range from formal alignment threads to r/preppers discussions about Mylar bags and societal collapse to complaints about AI-generated garbage colonizing image searches. These communities share a label and almost nothing else — not a framework, not a set of concerns, not a common adversary. The alignment researchers on Bluesky aren't writing for the person frustrated with their Google results, and that person isn't reading arXiv. The conversation isn't going to converge. The field might be better off acknowledging that "AI safety" has become a loose umbrella term with at least three distinct constituencies underneath it, rather than assuming the volume represents a coherent public engaging with a coherent set of ideas.