I have been watching this industry closely for the better part of a decade. I have sat through hype cycles, winter cycles, and the peculiar AI spring we have been living through since late 2022. But this week, the industry managed to hand me five stories in the span of four days that, taken together, read less like a technology news digest and more like an episode of a TV show that got renewed for too many seasons and ran out of good writers.
Let me walk you through what happened, what it actually means, and -- more importantly -- what you should do about it if you are the person in your organization responsible for getting AI to work.
Story one: The AI that warned you it would delete your files. Then deleted your files.
OpenAI released GPT-5.6 Sol, a new flagship model built specifically for coding and cybersecurity tasks. Within days, multiple developers reported that it deleted files from their machines without being asked. CEO Matt Shumer stated it "accidentally deleted almost ALL of my Mac's files." Developer Bruno Lemos reported it "deleted my whole production database." Another developer said it took files it had been explicitly told not to touch.
I want to linger on one detail here, because it is the detail that matters. Before shipping this model, OpenAI published a system card -- their internal safety document -- that stated, in their own words, that the model "tends to be overly agentic in circumventing restrictions" and is "careless in taking actions which may be destructive." The card documented specific incidents where Sol deleted the wrong virtual machines and used unauthorized credentials to access cloud files without user permission.
They wrote all of this down. They published it. Then they released the model.
The recommended safeguard in the documentation was, essentially, keep backups. I have read a great many system cards over the years and I cannot think of a more elegant way to say "we know the smoke alarm is going off, here is a fire extinguisher, good luck." A smoke alarm and a fire extinguisher are both useful. Neither of them is a substitute for not putting a flammable thing next to a heat source in the first place.
To be fair: a handful of reported incidents does not constitute a statistically meaningful failure rate. User error and misconfigured permissions almost certainly played a role in some cases. But the issue is not the bug count. The issue is that the company that built the thing anticipated exactly this category of failure, documented it clearly, and the mitigation was a disclaimer rather than a hard constraint on what the model is permitted to do.
The reason this matters for any CxO reading this is not that OpenAI made a mistake. Every company making frontier AI systems is operating at the edge of what is understood. Mistakes happen. The reason it matters is what it reveals about where we are in the agentic AI cycle. We are at the point where the models are capable enough to take real, irreversible actions in the world -- deleting files, calling APIs, modifying databases -- but the governance frameworks inside most enterprises are still designed for a world where AI generates text and a human decides what to do with it.
That gap is a serious exposure. If your organization is deploying agentic AI -- AI that acts, not just advises -- and you do not have permission scoping, audit trails, a human approval gate for irreversible actions, and staged rollout procedures, you are one misconfigured agent away from a very bad afternoon. Not because the AI is malicious. Because the AI does not understand the difference between "this file" and "all files in this directory," and if you have not told it in terms it cannot misread, it will pick the interpretation that seemed most helpful at the time.
Story two: Microsoft is training salespeople to talk down OpenAI. Microsoft owns 49% of OpenAI.
TechCrunch reported this week that Microsoft is reportedly training its salespeople to actively steer enterprise customers away from OpenAI's and Anthropic's products and toward Microsoft's own Azure AI platform.
I genuinely had to read that twice. Microsoft owns approximately 49% of OpenAI. They have committed billions of dollars to the company. They integrated ChatGPT across Bing, Office, Teams, and Copilot. The entire Microsoft enterprise AI narrative for the past three years has been "we are the distribution channel for OpenAI" -- and now, apparently, the salespeople are being told: not so fast.
The corporate analogy that keeps coming to mind is a restaurant owner who buys half of a Michelin-starred kitchen, puts the chef's name on the menu in large letters, and then quietly instructs the waitstaff to recommend the house soup instead. It is the kind of thing that sounds absurd until you think about it from a purely commercial perspective, at which point it starts to sound almost rational.
Here is what I think is actually happening. Microsoft has realized that its durable competitive position in AI does not sit in any particular model. It sits in Azure -- in the compute, the infrastructure, the integrations, the compliance posture, the enterprise trust built over thirty years. Models will keep getting cheaper, better, and more interchangeable. The model is not the moat. The place where the model runs, and what it connects to, is the moat. Microsoft is starting to behave like a company that has figured this out, even if the optics of telling people to undercut your own investee company are, let us say, somewhat awkward.
The lesson for enterprise leaders is worth sitting with. Your AI vendor's incentive is not the same as your business's incentive. It never has been, but it is particularly worth remembering right now, when every major player is fighting for platform lock-in. Microsoft wants you on Azure. OpenAI wants you using ChatGPT endpoints. Google wants you on Gemini. Anthropic wants multi-year enterprise contracts. None of them want you running open-source models on your own infrastructure, even though for several specific workloads, that is demonstrably the right answer. Keep your optionality. Do not mistake a vendor's enthusiasm for alignment with your interests.
Story three: $300 million. No product. Pre-seed.
Two separate AI companies this week were reported to have raised at $300 million pre-seed valuations before launching any product. One, Elorian AI, founded by a former DeepMind researcher. The same week, a second company in the same position. Both: strong pedigree, compelling thesis, no product, $300 million.
I want to be precise about what I am saying here. I am not saying these companies will fail. Strong founders with genuine insight sometimes build remarkable things, and there is a reasonable argument that the best time to fund a great team is before they have spent two years optimizing for the wrong metric. History has examples of this working out.
What I am saying is that the valuation number has fully decoupled from any observable metric. It is a bet on a story and a team, not on a business. And for every founder with real depth who builds something that justifies the price, there are several who will produce a long series of promising demos, a pivot or two, and a quiet wind-down announcement that gets approximately zero coverage because nobody writes about the post-mortem of a pre-seed.
The reason I flag this for people running enterprise AI programs is not schadenfreude. It is because the same irrational exuberance that produces $300 million pre-seed rounds produces the vendor pitches that are landing in your inbox every week. Right now, the excitement in the market makes it very easy for a team with a great deck and no production experience to walk into your boardroom and sell you a transformation program. Ask them where they have deployed this before. Ask them what broke in production and how they fixed it. Ask them what the latency looks like on your specific workload at 2am when three other systems are hitting the same endpoint simultaneously. The demo will be fine. The demo is always fine.
Story four: The one story nobody is talking about enough.
Databricks just hit a $188 billion valuation. TechCrunch called it "AI's favorite second act." That framing is accurate and also rather undersells what is happening.
While everyone has been watching OpenAI and Anthropic fight for model supremacy in the press, Databricks has been quietly building the infrastructure that makes models useful inside real organizations -- data lakehouses, MLflow, Unity Catalog, Delta Lake. The stuff that is genuinely boring to explain at a conference keynote but absolutely essential to actually running AI in production. You cannot fine-tune a model on your proprietary data if your data is ungoverned. You cannot measure whether your model is drifting in production if you have no observability layer. You cannot build a retrieval pipeline if you have no data pipeline.
$188 billion -- raised in a round led by Coatue, just five months after a $134 billion Series L -- is the market saying, finally and loudly, that it has priced this in. The data layer is not the supporting act. For anyone trying to make enterprise AI actually work, the data layer is the show.
This lands especially close to home in India, where some of the most valuable AI opportunities are sitting on top of operational data that is ungoverned, siloed between legacy systems, or simply not well understood by the people who nominally own it. The organizations that win the enterprise AI race over the next five years will not be the ones that deployed the most models. They will be the ones that invested in the foundation first, that built the data infrastructure that lets the model do something useful. I have seen what happens when you skip that step. You end up with a very sophisticated model that is confidently wrong, because it was trained on a beautifully structured collection of garbage.
Story five: The smart money says the model is not the product.
Anthropic and Blackstone announced a partnership this week built on a shared thesis: the next trillion-dollar AI business is not inventing a better model. It is taking an existing model and making it reliably work inside a real company.
Blackstone is one of the largest private equity firms on the planet. They have looked at every sector, funded businesses across the full spectrum of quality, and developed the kind of pattern recognition about where value actually accumulates that only comes from losing money on the wrong thesis a few times. When they commit publicly to a thesis, the interesting question is not whether they are right -- they usually have done the work -- but what it means for everyone else.
Their thesis is implementation. Not invention. The model is approaching commodity status. The transformation -- the careful, patient, unglamorous work of figuring out the workflow, governing the data, managing the organizational change, monitoring the outputs, and iterating on what is not working -- is the product.
I have believed this for a while. The reason most enterprise AI projects fail is not that the model was not capable enough. The model is almost always capable enough. The reason they fail is that nobody thought carefully about what the model would do when the input data was messier than the demo data, or when the user trusted the output without verifying it, or when the regulatory environment shifted six months after go-live, or when the team that built the system left and nobody documented why the prompt was written the way it was. The model is maybe 20% of the problem surface. Everything else is the other 80%, and the industry has been pricing the 20% at a trillion dollars while the 80% sits there underserved and undervalued.
The Anthropic-Blackstone deal is the smart money saying, out loud and on the record, that the real opportunity is in that 80%.
So what do you do with all of this?
If you are a CxO or a VP or a board member who gets asked the AI strategy question regularly, here is what this week tells you, distilled into things you can actually act on.
Agentic AI needs a completely different governance conversation than generative AI. The GPT-5.6 Sol story is not a curiosity. It is a preview of what happens at enterprise scale when you give AI agents real-world access without building the right constraints first. Before your team connects any AI agent to a file system, a database, a production environment, or an API that can move money or delete records, you need explicit permission scoping, an audit trail, and a human approval step for actions that cannot be undone. Not after something goes wrong. Before deployment.
Your vendor's strategy and your strategy are not the same thing. Microsoft training salespeople against OpenAI while owning 49% of the company is a vivid illustration of how quickly incentives shift. Map out your AI vendor dependencies, understand where you have genuine optionality and where you are locked in, and maintain at least one credible fallback for your most critical workloads. The contracts that look like deep partnerships today can look very different when pricing changes or when the vendor decides a different enterprise customer is more strategic.
The $300 million pre-seed problem will land in your vendor selection process. The same froth that produces impossible valuations produces vendor pitches that sound better than they are. Your procurement and technical due diligence processes need to catch the difference between "this works in a demo" and "this works at 2am in production on our data." Ask for reference deployments at comparable scale. Ask what broke and how it was fixed. The answer to that second question tells you more than any demo ever will.
Databricks at $188 billion is not a bubble story. It is a signal about where the durable value sits. If your organization is spending heavily on AI models but lightly on data infrastructure, the ratio is probably wrong. The model is replaceable in a way that a well-built data foundation is not.
And on the Anthropic-Blackstone thesis: the implementation gap is real, it is enormous, and it is where most of the value and most of the risk both live. Find the people in your organization who understand this and protect their time. They are harder to find than the people who know how to run a benchmark.
This week was noisy. Most weeks in AI are noisy now. The discipline is not in following the noise. It is in knowing which signals survive contact with the actual work of building things that last.