The Friday the Model Went Dark

Whether it comes back doesn't matter. That it could happen at all should change how you build.

Image created using AI tools

On a Monday in June, Anthropic released the most capable model it had ever built. By Friday evening, it was gone. Not slowed, not limited to certain regions. Gone, for everyone, everywhere.

I have been sitting with that all weekend, and I want to share where my thinking landed, because I don’t think the lesson is the one the headlines are reaching for.

Here is what happened, told simply. Anthropic released Fable 5, and the model beneath it, Mythos 5. Teams across the industry spent the week building it into real work. Then the U.S. Commerce Department issued an export control directive: these models could not be used by any foreign national, anywhere, including foreign-born employees working inside U.S. offices (and you can imagine why it matters to me, and to you, if you are foreign-born). There was no clean way to honor that order in real time, so the only path to compliance was to switch the models off for everyone. And so they did. The most capable thing on the market went dark on a Friday night, because of a decision no customer was part of.

I want to be careful with the facts, because this story is being told in several versions, and some carry more confidence than the record supports. The verified spine is narrow. A government directive, citing national security, tied to the model’s cyber capabilities and a jailbreak technique. The company disagrees, calls it a misunderstanding, and says it is working to restore access. The more dramatic threads, who called whom, who set it in motion, are still unsettled. I would rather build on what is solid than on what is satisfying.

What is solid is enough to learn from.

This fits in an arc

Every infrastructure we now take for granted went through the same passage. There was a season when it was new and astonishing, and we built on it before we fully understood what we were leaning on.

Be it Electricity, the early eb or the Cloud.

Each one moved from “remarkable capability” to “thing we assume is simply there.” And each one, somewhere along that path, had a moment that reminded everyone it was not as solid as it felt.

Frontier models are early in that arc. They are astonishing, they are everywhere, and we have started to treat them the way we treat electricity. Something that is just on. Friday was a reminder that we are not there yet. The most capable models are still the newest part of the stack, and the newest part is always the part most exposed to forces that have nothing to do with engineering.

That is not a criticism of any one company. The same structure would hold for any frontier model from any provider. It is simply where we are in the arc.

A layer above

When a company adopts a model, it negotiates the things it knows how to negotiate, namely, uptime, latency, committed spend, data handling, support etc. Those terms feel like the boundaries of the relationship, and most of the time they are.

What this week showed is that there is a layer sitting above all of that and that is regulatory, geopolitical, national. And that layer does not read your service agreement. When it moves, the terms you negotiated still hold, they just stop being the thing that decides the outcome. The capability can be withdrawn by a force you have no seat across from.

This is worth naming plainly as something the field is now ready to see clearly.

We have understood model risk mostly as “will it perform.” This week added a second dimension: “will it remain available to me, and who decides that.” Both are real. We have simply been measuring one and assuming the other.

Why “it will come back” is not the lesson

It is tempting to wait this out. Access may well be restored. The disagreement may resolve, and the model may return as if the week never happened. And then the easy move is to file it under “strange few days” and carry on.

It’s worth gently resisting that. The specific outcome is not the lesson. The lesson is that the event was possible at all. A capability that hundreds of millions of people were using could go to zero overnight, lawfully, with no warning. Whether it stays gone for three days or three months does not change what it taught us about the shape of the risk. A thing that can happen once on a Friday can happen again on a Tuesday.

The narrow lesson is “this model carried risk.” The useful lesson is “leaning on any single model this completely carries risk.” One sends you shopping for a different vendor. The other invites you to look honestly at how you have built.

A question worth pondering over

So here is the question I have been thinking over, and I offer it as a genuine prompt rather than a rhetorical one.

If your primary model went dark this Friday, not slower, dark, what happens on Monday?

Picture it concretely. Which workflows stop. Which customers notice. How long before something else carries the load, and how much harder is it carrying. Do you know the answer already, or is it something you would discover in real time, under pressure, the way teams often discover their backups only when they finally reach for them.

Most organizations cannot answer this cleanly yet, and I don’t think that reflects poorly on anyone. The question simply was not urgent until this week. The capability was too good and too available to imagine it absent. That is exactly the condition under which dependence gathers quietly, when the thing we depend on feels too solid to question.

What I think resilience actually asks of us

I don’t believe the answer is fear, or stepping back from frontier models, or treating capability as a liability. Fear and stepping back is never a solution to any problem. The capability is real and the value is real. The answer is quieter than that, and frankly harder. It is knowing your own exposure well enough to act on it before the moment forces your hand.

That means being able to say, with specifics, where you are concentrated. It means having a fallback you have actually tested, not one you assume will be there. It means treating “what is our dependency profile” as a question you can answer at any time, rather than one you reconstruct in a hurry. None of this is dramatic. It is the difference between an organization that has a plan and one that becomes the plan, improvised live, while the screens turn red.

In its own backhanded way, Friday was a gift. It took a quiet, structural risk and made it loud, and dated, and undeniable, at a cost that for most of us belonged to someone else. That is the least expensive way to learn an expensive lesson. The expensive way is to learn it when the model that goes dark is the one your own business is standing on.

The model came back, or it will. The question it asked is going to stay with us a while longer.

What is your fallback plan if your primary model goes dark on a Friday? I would truly like to know how you are thinking about it. Reply and tell me.

Until next week…

Founder and CEO | SANJEEVANI AI