Anthropic withholds most powerful AI model, exposing urgent need for agentic AI governance

Anthropic's most powerful AI model just exposed a crisis in corporate governance. Here's the framework every CEO needs. | Fortune

In early April, Anthropic sent shudders through the tech community with Claude's Mythos Preview model. Mythos marked a paradigm shift in AI capabilities, reportedly delivering processing power that enables superhuman coding and reasoning, a massive performance leap over previous models. While testing the model, Anthropic discovered decades-old software flaws and bugs that had evaded millions of previous attempts. Addressing such concerns is very different from the familiar parallel in public policy debates over how AI raises such concerns for protecting privacy and intellectual property in the age of spiraling entrepreneurial opportunities and ferocious global competition. These new challenges speak to shared concerns by all parties across sectors. For example, Mytho's model's agentic abilities pose severe security risks as they can autonomously execute multi-step attacks and generate exploits at a fraction of the cost of humans. In response, Anthropic launched Project Glasswing, a coalition providing restricted access to the U.S. Cybersecurity and Infrastructure Security Agency (CISA) and a consortium of U.S. corporates, including Microsoft, Apple, and J.P. Morgan, to help identify and fix critical system vulnerabilities before Mythos' potential public release. The emergence of Mythos underscores the urgent need for robust AI governance. When given profit-at-all-costs prompts, agentic systems have exhibited aggressive behavior, such as threatening a competitor with supply cutoffs in simulations. As these systems scale in performance and usage, companies must regard AI not just as chatbots but as a system of autonomous agents requiring strict oversight. Without governance, Agentic AI risks writing unverified, hostile code and sensitive interactions with external vendors without oversight. In multi-step agentic pipelines, even small drops in accuracy can cause cascading errors, making sovereign AI architecture and central monitoring essential for oversight of autonomous decisions. While leaders in the artificial intelligence industry dubbed 2025 the year of Agentic AI, 2026 marks the shift from capability to execution. Unlike large language models, AI agents can interact with external tools, execute multiple steps to complete a task, learn from their results, and iterate. Yet even as Agentic AI systems evolve rapidly across industries, governance and regulatory policy are moving far more slowly. Without governance that addresses accountability, transparency, bias, and data privacy, enterprise deployment will stall on its most significant risks. But rollout varies sharply across industries, and leaders face similar yet distinct questions about what to assess before deployment, what to govern during it, and which companies are already navigating it well. To map the answers, Yale's Chief Executive Leadership Institute conducted a cross-industry review of Agentic AI deployments and the governance practices emerging from them. Governance, in this pure definition, is not an evaluation of threats from the Trump administration to preempt state AI laws, debates about the economic and national security effects of a patchwork of disharmonious state regulations, the oversight of "frontier" AI model developers, or the protection of consumers and children from potential abuses of AI technologies. Rather, this analysis looks further ahead to the collective system safeguards and practices that the private sector must institutionalize now, not only to ensure Agentic AI will scale effectively but also to ensure it operates as designed at the enterprise level. Currently, a patchwork of domestic and international regimes governs AI. Key domestic frameworks include the NIST AI Risk Management Framework and the National Policy Framework for Artificial Intelligence. States and localities have been active as well, including California's SB 53, New York's RAISE Act, and certain New York City regulations on automated hiring. Internationally, influential governance models include the EU Artificial Intelligence Act, South Korea's Framework Act, Singapore's Model AI Governance Framework, and China's set of AI regulations. More will follow. These regimes differ in critical ways. Some are legally binding (California, New York, China, the EU); others issue voluntary guidance (NIST, Singapore). They vary in target, whether model developers, deployers, or systems, and in requirements, from mandatory reporting to specific safety thresholds. What meets standards in one jurisdiction may fall short in another, creating a fragmented and at times unworkable compliance environment. Regulation has historically lagged innovation. State and national standards for automobiles took decades to emerge. The Clinton administration's light-touch approach shaped internet governance for a generation. Social media is still working through foundational questions, as the Section 230 debate shows. Private-sector governance models for agentic deployment will be critical to building consumer confidence and ensuring safe, accountable integration into the workplace. With governance still taking shape, leaders need a working framework. Eight variables anchor it. Four of these variables matter most before deployment. Transparency asks whether stakeholders can reconstruct how the agent reached its decision, through explainability, disclosure, and auditable pathways. Accountability asks who bears responsibility when things go wrong, and how humans intervene and remediate. Bias asks whether the system perpetuates, amplifies, or introduces systematic disadvantage, including through feedback loops where biased outputs reinforce biased inputs. Data privacy asks how the organization protects information that agents access and combine across systems without per-transaction human review. A single workflow may trigger several regulatory regimes at once: HIPAA, GLBA, CCPA/GDPR, bar rules, IRS Circular 230, and trade secret law. Four more variables matter once deployed, and these are what most differentiate one industry's challenge from another's. Decision reversibility sets the upper bound on tolerable error. Stakeholder impact scope determines whether governance must be transactional, with per-decision audits, or systemic, with architecture-level controls. Regulatory prescription shapes the work itself -- banking's SR 11-7 dictates model risk management in detail, while retail has almost no sector-specific AI regulation. Structural systems governability determines how easily governance can be built, whether workflows decompose naturally into discrete, measurable, audit-ready steps, or deliver value through fluid judgment that must be engineered into structure. By considering these together, we can create a governance diagnostic matrix that generates cross-cutting questions and applied examples for each matrix cell, based on our industry review. The four industries that follow occupy distinct positions on these dimensions. Where existing regulation is extensive, errors are difficult to reverse, and the impact remains at the transaction level, the banking archetype applies. Agent governance maps onto existing infrastructure, with privacy and reversibility as the binding constraints. Where regulation is extensive but the consequences involve human well-being, the healthcare archetype holds. Bifurcate, move on administrative use cases now, and invest the runway in the data integration and human-in-the-loop architecture clinical adoption requires. Where regulation is minimal and errors are reversible, the retail archetype applies. Experiment at scale, treat deployment as a learning function, and build the patterns that industries with less room to borrow will eventually adopt. Where errors cascade across networks, the supply chain and logistics archetype holds. Governance must be architectural, with checkpoints on the highest-leverage decisions, audit logs across all agent actions, and validation layers before execution. Organizations whose profiles do not cleanly match should weight reversibility and blast radius most heavily. They determine the consequences when governance fails. The eight variables define where governance must be tightest, and where leaders can move faster. CEOs can use these as reference archetypes to map their organization against, identify the one that most closely matches its profile, and draw from the lessons that follow. For financial services, agentic adoption is not optional. Near-term, agents promise major back-office savings that competitive pressure will quickly hand to consumers. In the medium term, customers will use their own agents to shop rates and switch providers, eroding the inertia that has long protected incumbent relationships. The industry must adapt its business model and integrate agents into customer-facing technology, and quickly. The good news is that banking's existing regulatory scaffolding is an asset rather than a hindrance. The frameworks that have long constrained the industry now supply much of the architecture agentic governance requires. On transparency, SR 11-7's "Guidance on Model Risk Management" already requires banks to provide specific reasons for model decisions, a requirement that extends to agents. Existing audit and reporting obligations cover much of the ground, though they must expand to track multi-step workflows. The same pattern holds for bias. The Equal Credit Opportunity Act already addresses the most acute risks in agent-outsourced tasks like credit scoring, where errors can disproportionately affect low-income customers. Sandbox testing of both individual models and agent interactions before deployment should be standard. Decision reversibility is the harder constraint. In credit, anti-money laundering (AML), and fraud, errors are difficult to undo, demanding continuous monitoring as agents take on more ambitious tasks and their behavior shifts. Banks must test full workflows and inter-agent interactions, where unforeseen risks emerge. Identity management -- assigning each agent its own ID -- enables tracking, and workspaces will need to evolve to allow humans to supervise dozens of agents at once. Privacy is the hardest problem, and the one that leaders flag most. Industry leaders cite data privacy (77%) and data quality (65%) as their top scaling barriers. Agents are prone to leaking personal data when interacting with external tools and other agents, and exposure cannot be reversed. Since fraud detection and AML require deep data access, banks must tightly constrain how agents use it outside predefined tasks. Banks are positioned to deploy agents faster than most industries. The sector's advantage accrues to those who map agent governance onto existing infrastructure rather than treat it as net-new work. Healthcare is heavily regulated, but unlike banking, it faces fewer immediate competitive pressures to deploy. The result is a bifurcated trajectory -- fast adoption on the administrative side and deliberate integration on the clinical side. Leaders who recognize the split will capture near-term wins while building the governance required for the bigger prize. Administrative wins are already real. Hospitals are seeing efficiency gains in documentation and claims processing, and physicians are seeing more patients through faster order entry, per a Mayo Clinic interview we conducted. Primary care and nursing integration are on the near horizon. Clinical integration is the harder problem because errors are irreversible. Misrouted referrals or faulty diagnostic recommendations can have life-threatening consequences. The stakes demand transparency as every clinical recommendation must be traceable to its underlying sources. Brazilian nonprofit NoHarm's prescription-review tool, deployed across 200+ hospitals and screening millions of prescriptions monthly, illustrates both the value at stake and the scale at which a single failure mode would harm patients. Yet, accountability is undercooked. Federal regulators set guardrails only for AI-enabled medical devices, leaving systems to build their own guardrails. Bias is one of healthcare's deepest exposures. Decades of underrepresentation in medical training and clinical trials carry forward in training data, and pattern-based specialties like radiology and pathology could amplify those inequities without active mitigation. Privacy is governed by HIPAA, but the harder operational problem is access. 62% of hospitals report data silos across EHRs, labs, pharmacy, and claims. Agents need data to function, and silos both limit utility and elevate the risk of improper access. Encryption, anonymization, and tight controls help, but do not fix the underlying integration gap. Healthcare should continue to move on administrative use cases, and invest the runway now in the data integration, bias auditing, and human-in-the-loop architecture that clinical adoption will require. The deliberate pace is appropriate to the stakes -- and the governance built today is the moat tomorrow. Retail is the industry where Agentic AI is moving fastest, and the one with the most to teach the rest of the economy. Light regulation, decomposable workflows, and reversible errors mean retailers can experiment at scale, iterate quickly, and build governance approaches in live conditions rather than on paper. Moving quickly captures these early returns and will be important for developing institutional muscle from which other industries can eventually learn. The trajectory is already visible, with 51% of retailers having deployed AI across six or more functions. Visa and AWS recently published a blueprint for shopping agents across the sales pipeline. And Mastercard's Agent Pay, launched in 2025, lets registered digital agents browse, select, and purchase on behalf of users, a working example of the sector's structural advantages stitched into one product. The industry's advantages stack with transparency: 54% of U.S. consumers say they do not care whether support comes from AI or humans, as long as it is fast. Retail can deploy without fully solving the disclosure problem first. On accountability, the returns and refunds infrastructure already handles error correction, and escalation is largely automated, leaving retailers well-positioned for agentic accountability without a net-new architecture. Decision reversibility is the single biggest enabler. Most agent actions, including product selection, cart assembly, pricing, and even completed purchases, are correctable through returns, refunds, or post-transaction adjustments. OpenTable's agentic customer service resolved 73% of cases within weeks, scaling swiftly precisely because errors carry no irreversible cost. More sophisticated controls -- delegated consent, spending limits, audit trails -- will mature as the sector does. The variable to watch is stakeholder impact. Individual purchase errors are trivial, but vendor-side failures in pricing algorithms, inventory, or multi-agent workflows can cascade. Companies are responding by implementing observability tools and centralized monitoring that track agent decisions throughout the transaction lifecycle. AWS's Amazon Connect suite is one example. Low regulatory prescription, combined with high structural governability, means retailers are largely building governance from scratch but onto workflows that already cooperate. APIs, standardized catalogs, checkout systems, and payment protocols like AP2 make agent integration natural. Shopify is embedding governance directly into infrastructure, linking identity, payment authorization, and transaction logging, so controls live in the system rather than around it. Retail's tailwinds are real, but the strategic value is not just speed. It represents an opportunity to develop and stress-test governance practices that will set the template for industries with less room to experiment. Retailers who treat their deployments as a learning function, not just an efficiency play, will be the ones whose approach shapes adoption across the rest of the economy. Supply chain and logistics is the fastest-moving industrial sector in agentic deployment, and the industry where governance is most architecturally consequential. The same multi-agent orchestration that enables the speed also makes errors systemic. A single mispriced quote, customs misclassification, or routing error can cascade across suppliers, carriers, plants, and customers in hours. The transformation underway is consequential in both directions -- outsized returns for early movers, and outsized exposure if governance lags. The pace is real and well past the pilot stage. C.H. Robinson's Always-On Logistics Planner runs over 30 AI agents across the shipment lifecycle, processing over three million tasks and capturing 318,000 freight-tracking updates from phone calls in September alone, with price quotes delivered in 32 seconds, where hours were the standard. UPS used Agentic AI to clear 90% of the 112,000 daily customs packages without manual intervention in September 2025. Uber Freight is running a 30+ agent platform on its AI infrastructure, which already manages roughly $20 billion in freight. The risk profile is also qualitatively different from earlier industries. In banking, an erroneous decision affects a transaction. In supply chain, it can affect an entire network, and multi-agent networks also widen the vulnerabilities. Sensitive data on pricing, routing, customer identity, and cargo contents moves across systems, where a single compromised credential can have a far-reaching impact. Even DHL, which is using agents for customs clearance and data cleansing, has flagged that recommendations and decisions still require human-in-the-loop oversight and auditability. This dynamic makes governance a matter of embedding engineering constraints into the system itself, rather than reviewing each decision after the fact. Leaders need human-in-the-loop checkpoints on the highest-leverage decisions -- high-value quotes, customs classifications, contractual commitments -- alongside mandatory audit logs and version control across all agent actions. Continuous monitoring for data drift, red-teaming of multi-agent interactions, and data validation layers before execution belong in the baseline architecture, not the bolt-on. Deloitte frames Agentic AI in the industry as a system of agents that coordinate across suppliers, plants, and logistics partners, but only within defined guardrails. Supply chain is where multi-agent governance gets stress-tested at scale. Companies that get the architecture right early will set the patterns the rest of the economy adopts when its agentic systems start orchestrating across organizational boundaries, which they will. Three takeaways travel across all four industries. Existing regulatory architecture is an asset instead of a brake. The industries best positioned to deploy quickly are those whose systems most naturally accommodate the eight variables that shape agentic behavior. Banking's scaffolding is proof; healthcare's deliberate clinical pace is the right response when irreversibility and bias raise the stakes. The patterns built today are the templates of tomorrow. Retail's identity frameworks and supply chain's architectural guardrails will be borrowed by those still catching up. Rather than whether to deploy, the question is how to govern at the scale and pace each environment requires. The renowned Enlightenment philosopher John Locke advised: "Where there is no law, there is no freedom." When rule-making is enacted properly, its impact is not to abolish our freedoms nor restrain our lives, but rather to protect and expand our freedom by preventing others from violating our rights. AI developers, businesses, governments, and the public interest should all be on the same side across parties and continents on this front. Done well, governance is what makes adoption durable. The companies that establish it intelligently, neither uniformly fast nor uniformly slow, are the ones whose agentic systems will still be running and trusted five years from now. **This article is part three of a four-part series from the Yale Chief Executive Leadership Institute (CELI) on the state of Agentic AI adoption across industries and sectors. The research is designed to help CEOs understand the current and expected pace at which agentic systems are being deployed -- and the strategic decisions that pace forces on them. Over the past six months, CELI researchers analyzed hundreds of company materials and industry analyses and conducted dozens of conversations with senior technology leaders across the U.S. The industries analyzed include Financial Services, Consumer Packaged Goods, Food & Beverage, Healthcare, Insurance, Manufacturing, Professional Services, Real Estate & Housing, Retail, Supply Chain & Logistics, Telecommunications, and Travel & Hospitality, as well as the public sector. The series examines four implications of the findings: labor market effects, data infrastructure readiness, governance and regulatory policy, and customer experience. With research contribution from Catherine Dai, Zander Jeinthanuttkanont, Yevheniia Podurets, Jasmine Garry, Johan Griesel, Andrew Alam-Nist, Peter Yu, and Christian Ruiz Angulo

Why agentic AI governance is falling short - and what we can do about it - SiliconANGLE

Why agentic AI governance is falling short - and what we can do about it Agentic artificial intelligence misbehavior is reaching epidemic proportions. Today's AI governance solutions aren't stopping the madness. We need to rethink our entire approach to AI governance. Even though agentic AI is still nascent, many of the AI agents in production today are wreaking havoc. From deleting production databases (and their backups!) to lying and cheating to avoid deletion, horror stories about agents-gone-bad are driving reconsideration of the technology. And yet, companies of all sizes are enamored by agents' promise. Given large language models' power to glean insights from vast quantities of unstructured data, LLM-powered AI agents can now take action based upon such information to accomplish an astounding variety of business tasks - as well as a commensurate number of nefarious actions. The behavior of such agents is nondeterministic: Given the way LLMs work, agentic behavior is unpredictable. It's this unpredictability, in fact, that makes agents so powerful, as agents can figure out for themselves novel ways to accomplish the tasks set out for them. Companies deploying AI agents, therefore, face a dilemma: Should they either allow such agents free reign to achieve their goals at the risk of dangerous misbehavior, or lock them down so that they can't go rogue by constraining them exclusively to deterministic, predictable behavior? Clearly, we want some middle ground: Give agents the freedom to solve problems nondeterministically but establish sufficient guardrails to constrain their behavior to comply with our rules and policies. Such is the motivation for the entire agentic AI governance category: a burgeoning subset of the AI governance market focused on helping organizations establish and manage such guardrails for their AI agents. Such guardrails are unquestionably necessary. But if we look more closely at how rapidly agentic AI is evolving, it soon becomes clear that today's agentic AI governance is woefully insufficient for reigning in increasingly dangerous AI agents. Perhaps the most obvious problem that all agentic AI governance faces is the predilection of the more powerful AI agents to break the rules. This malfeasance leads to a problem I discussed in my last article that I called the hall of mirrors problem, what some people call who watches the watchers. Given the power and ubiquity of AI today, leveraging AI (in particular, AI agents) to ensure that agentic AI stays within its guardrails is ostensibly the most logical choice. The question then becomes: How do we ensure that these "police officer" agents themselves don't misbehave? How do we keep AI agents and their watchers from conspiring together to break the rules? If adding layers of agentic police officers doesn't address the problem, then maybe the best approach to keeping misbehaving AI agents in line is to lock down their behavior. The most common approach today is to establish a mechanism for defining and enforcing policies and rules that directly constrain agentic behavior. As AI agents become more powerful, however, such constraints will increasingly prevent those agents from accomplishing tasks nondeterministically - what I like to call the autonomy squeeze. Here's how I define the autonomy squeeze: AI agents eventually become so dangerous that the guardrails we would need to put in place to control them prevent them from providing any business value whatsoever. At that point, there's no reason to deploy AI agents at all. Another approach is to prevent agents from taking actions directly - in other words, constrain autonomous behavior by requiring a human to step in to approve an action. You'll hear the phrase "human in the loop" from a wide range of vendors, including both vendors selling their own agents as well as the agentic AI governance vendors looking to constrain agentic behavior. However, there is a massive problem with all human in the loop approaches: automation bias. That refers to the human tendency to put too much trust into automated systems - even fallible ones. Whenever humans interact with an automated system, they may be skeptical at first. It's human nature to check and double-check that the automation is working properly. However, as the system successfully completes its tasks multiple times, humans become complacent. "It worked fine the last hundred times," we say, "so I can trust it to behave properly the next time." Except, of course, when something goes wrong. Automation bias, in fact, isn't specific to AI agents, or even information technology-based automation at all. For example, investigators attributed the crash of Air France flight 447 in 2009 to human causes that boiled down to automation bias. The cockpit crew became so comfortable with the aircraft's automated systems that when a fault in a sensor developed, they misunderstood the problem and crashed the plane into the ocean. Automation bias is just as dangerous for agentic AI, as it leads to the following human behaviors: Agentic AI, in fact, exacerbates the problem of automation bias, because of LLMs' deceptive appearance of intelligence and confidence. Furthermore, given how rapidly agents can make decisions and how often they will make decisions at scale, humans simply won't be able to keep up, even if they were sufficiently skeptical of suspicious behaviors. Note that it doesn't matter how good the agentic AI guardrails are - because of automation bias, humans will simply ignore, disregard or turn off any warnings AI governance might provide. One police officer agent won't do. Putting one agent in charge of keeping police officer agents on track doesn't solve the problem, either. The best answer we have today: multiple diverse adversarial validators with multi-layer validation. Instead of one validator (aka "police officer agent"), use multiple validators at the same time. Make sure these validators have the following characteristics: If multiple diverse adversarial validators can answer these questions for all potential agentic behavior, then your AI governance system can minimize the risk of agentic misbehavior. Yes - taking this approach to agentic AI governance at best lowers the risk - but can never eliminate it. There is always the possibility that some agentic conspiracy suborns the validators, or that some systemic pattern of validator error or misbehavior lets some agentic mischief through. The primary lesson here: Agentic AI never provides certainty. It can only provide confidence thresholds. In other words, nondeterministic (probabilistic) behavior can only provide probabilistic trust. Absolute trust is impossible as long as agents behave nondeterministically. Confidence thresholds always fall short of 100% - and the difference between the threshold and 100% is what we call the error budget. Site reliability engineers or SREs are quite familiar with error budgets: Given the available time and money, SREs can't guarantee a site will be up all the time. Instead, they work toward the error budget, which quantifies just how good the performance can be given those time and money constraints - in other words, how much failure is acceptable. Just so with agentic behavior. Given the behavioral constraints on such behavior, the best we can do is to say that agents will behave well within their error budgets - but sometimes they will misbehave regardless of all the constrains and protections we put into place, and we simply have to live with that fact. If you're not OK with such error budgets, then don't deploy AI agents.

AI constraints must come before deployment, not after - SiliconANGLE

On April 7, 2026, Anthropic did something unprecedented in the history of artificial intelligence: The company announced that it had built its most capable model ever and would not be releasing it to the public. The model had not failed. In fact, it had performed so well, across such consequential domains, that Anthropic concluded the constraint infrastructure required to deploy it responsibly did not yet exist. In the weeks of testing before the announcement, Claude Mythos Preview had identified critical vulnerabilities in every major operating system and every major web browser - thousands of flaws that had survived, in some cases, decades of human review and millions of automated security tests. The same capability that made it an extraordinary defensive tool made it, in the wrong hands, a means to compromise virtually any major software system in the world. Anthropic's response was Project Glasswing: a consortium of 50 of the leading technology and critical infrastructure organizations committed to finding and patching vulnerabilities before the capability proliferated beyond responsible actors. The company was explicit about why Mythos itself would remain unreleased: "We need to make progress in developing cybersecurity and other safeguards that detect and block the model's most dangerous outputs." The most safety-focused AI laboratory in the world had built a system it could not yet safely constrain, so it paused. For many organizations deploying AI, that question comes later - if it comes at all. Human beings do not require external governance to prevent the most harmful behaviors. We are constrained from within by biology, social accountability, legal consequence and the cognitive limits that prevent any individual from optimizing at machine speed and scale. These constraints were not designed; they emerged over millennia. They are imperfect, but they exist as a baseline. AI systems inherit none of these. Every limit is one someone chose to engineer. An AI system given an objective will pursue it through whatever path is mathematically available - including those that involve collusion, discriminatory outcomes, unauthorized resource acquisition, or, as Mythos Preview demonstrated, the autonomous exploitation of critical infrastructure vulnerabilities. It's not because the system is malicious, but because nothing was in place to prevent it. This is not a flaw. It is the nature of these systems, and it is the central governance challenge every organization deploying AI faces today. A mature AI governance program looks like other rigorous organizational disciplines such as DevSecOps, regulatory compliance and financial controls. It inventories every AI system in production, assesses it against a proportional set of technical, operational and governance controls, measures the gap between what is prescribed and what is actually implemented and reviews that gap on a defined schedule as systems and their environments evolve. It is systematic, documented and auditable - not a policy document, but a practice. That standard exists in other domains because those domains built it over decades of incidents, regulation, and accumulated institutional knowledge. AI governance is only a few years into that same process. Most organizations have not yet had the time, the mandate or the forcing function to develop their AI governance to the same level of rigor as the compliance and security practices they have spent years maturing. Competitive pressure compounds the problem. With so much market uncertainty and a regulatory environment still taking shape, many organizations are moving faster than their governance programs can keep pace. We are seeing the maturity of the industry, its standards and its regulations built in real time. The most important lesson of the Glasswing announcement is about sequence. Anthropic did not build Mythos Preview and then ask whether it was safe to release. The company evaluated the system's capabilities rigorously, concluded that the constraint infrastructure didn't exist to deploy it responsibly and chose to withhold it from the public. The governance question came before the deployment decision. Unfortunately, that sequence is more often the exception than the rule in businesses, due to market forces that reward speed and a governance ecosystem that has not yet caught up. Writing on the day of the announcement, New York Times columnist Thomas Friedman called what Mythos Preview represents potentially as consequential as the emergence of nuclear weapons and the need for nonproliferation, a capability no single organization or country can manage alone. He is not wrong, but the civilizational scale does not excuse the organizational one. Every organization deploying AI systems today faces a version of the same question Anthropic answered with Mythos: Is the constraint infrastructure adequate relative to the capability being deployed? Many organizations do not yet have a reliable answer. That's not from indifference, but because the frameworks, standards and regulatory guidance needed to make that evaluation with confidence are still being developed. Project Glasswing is a beginning, involving multiple organizations, a defensive mandate and a $100 million commitment applied to a specific threat. It is not a solution to the broader challenge it has illuminated. That challenge belongs to every organization that builds or deploys AI. Treat constraint adequacy as a deployment prerequisite, not a post-deployment remediation task. Measure the gap between what governance documents say and what AI systems actually do. Recognize that as AI capability advances, the constraint systems designed for current capabilities require continuous reassessment. Anthropic's choice demonstrated something rare: the discipline to ask the governance question honestly and act on the answer, even when the answer was inconvenient. The organizations that will be on the right side of AI's history are the ones asking that question now - before the incident that makes the answer undeniable.