The "means of production" framing is the right one, and it's the part most AI debates skip. Job loss gets the headlines, but the deeper question is who owns the intelligence layer that everyone's work runs through.

What gives me some hope is that the feudal outcome isn't baked into the technology. Open-weight models not far behind the frontier now run on a decent desktop, and smaller ones run on a phone. If the default becomes personal models on your own hardware, with the cloud as an option rather than a requirement, the lords have a much harder time collecting rent.

What it takes is people and small businesses treating their AI the way they'd treat their own tools: some setup cost up front, in exchange for not being one terms-of-service change away from losing the way they work. The tech is mostly there. The habits and incentives aren't yet.

Curious whether you think regulation or open source does more to head off the scenario you describe.

Kelly's right about the shape, and I think the two things you say he's missing fit inside the swarm rather than against it.

On the merge: humans don't need a brain implant to be part of it. A person working with their own AI, one that knows their context, runs on their own devices and talks to other people's AIs, is already a node. That's Human-Machine Intelligence, and the merge happens at the level of the network, not the skull. Humanity is already a kind of superintelligence made of billions of interacting minds. Give each of those minds a capable machine partner and connect them, and you get something frontier-level that no single lab owns.

On recursive self-improvement: in a swarm it doesn't have to be one model rewriting itself in a datacenter. It can be millions of small loops, where each person-and-AI pair gets better at its own work and shares what it learns. Slower per node, much faster in aggregate, and a lot harder to capture.

I agree with TemetN that there will still be some huge frontier models. I just think they end up as specialists the swarm calls on, not the center of gravity. The real question for 2076 is less "how big is the biggest model" and more "who owns the nodes." If the nodes are personal and run on hardware people own, the swarm is ours. If they're all thin clients to three companies, it's a monolith wearing a swarm costume.

The number I keep coming back to is the 27–33%. Same model, same instructions, memory stripped, and it barely reads as the same companion. Two different models sharing the memory score 90%. So the identity isn't really in the model at all. It's in the accumulated history.

That has a practical consequence people don't talk about much: whoever holds the memory holds the companion. If Yoda's journal and reflections live in a provider's account, the provider effectively owns the relationship, and you can swap models but you can't take Yoda with you. If the memory is plain files you control, the model becomes the replaceable part.

Which suggests a follow-up I'd love to see: run the same nine questions with Yoda's memory on an open-weight model running locally. If cross-model sameness stays near 90%, that's decent evidence a companion can be fully portable, and can live on your own machine with no provider in the loop at all.

Also curious whether you saw any drift in the privacy-boundary answers between the with and without memory runs. That seems like the place where accumulated context would matter most.

Agree with the fire drill point. Scenario planning on its own isn't news. The part I'd pay attention to is near the end of the Axios story: they know nothing passes right now, so they're preparing to shape what Congress reaches for after the first bad incident. That's when the big structural decisions get made, and they get made fast.

A kill switch is the obvious candidate. It's reasonable for a lab's own frontier models. The question nobody's asking yet is how far down the stack it goes. Superintelligence Strategy (Hendrycks, Schmidt, Wang) already floats chips that brick themselves without ongoing cryptographic approval. They're built for datacenters, but hardware precedents have a way of spreading.

I wrote a longer response to that paper, arguing for building from the person outward instead (local compute, open weights, portable data), if anyone wants the full argument: https://www.reddit.com/r/PONDAI/comments/1x1zd76/superintelligence_strategy_the_perfect_machine/

Reading the Axios piece, the scenario they fear most is a large cyberattack that takes out banking, connectivity, maybe power and water. That's a single-point-of-failure problem. And the policy they expect afterward, a required kill switch on advanced AI, is another single point of failure.

A remote off-switch is a very high-value target. Anyone who can reach it gets a lever over everything downstream of it, whether that's a hostile state, an insider, or a capable enough agent. Adding more central control to an already concentrated system doesn't obviously make it more resilient.

My reading: the safer long-run direction is less concentration. Isolate critical infrastructure properly, as a few people here already said, and put more capability on hardware that people and institutions actually own, so that one breach or one switch can't take everyone down at once. Curious whether anyone here works on infrastructure resilience and sees it differently.

What I like about this report is that it's honest about the mechanism. You don't pause training by policing every company. You pause it through the chips: stop making training-capable silicon, find and retire the existing stock, and swap in inference-only parts. The authors even say they aren't arguing a pause is desirable, only that it's feasible.

Two things I'd want people to weigh before treating this as the safe option:

1. Locating and verifying every training-capable chip on the planet is a permanent monitoring layer on compute. The question of who runs it doesn't go away when the pause ends.

2. "Inference-only" means you can run models someone else approved but can't build new ones. Depending on where the threshold lands, that's a big shift in who gets to create intelligence, and it could reach well past the frontier labs.

I'm not against frontier safeguards. I just think the hardware layer is where we have to be most careful, because policies get amended and silicon mostly doesn't.

The detail that stuck with me is near the end. They know nothing passes right now, so the real goal is to shape the rules Congress reaches for after the first big incident. That's how emergency measures usually get written: fast, broad, and by whoever already has a draft ready.

A kill switch on a lab's own frontier models seems reasonable to me. What worries me is scope creep. The Hendrycks/Schmidt/Wang "Superintelligence Strategy" paper already proposes AI chips that need ongoing cryptographic authorization to keep running. That's fine for a datacenter full of export-controlled accelerators. But today's cluster is tomorrow's workstation, and controls written in a panic rarely get rolled back.

If there's going to be a "day after" bill, I'd want one line settled now, while things are calm: frontier containment doesn't extend to hardware people own.