For years, the public argument about artificial intelligence has been conducted at the summit. Which lab has the strongest model. Which country controls the most advanced chips. Which company can afford the largest training run. This framing is understandable, but it is incomplete. By mid-2026, the more consequential contest is taking place at a lower altitude, in places that rarely attract headlines: application programming interfaces, logging formats, incident reporting schemes, evaluation templates, identity layers, provenance standards and procurement clauses. These are the seams between systems. They look mundane until one asks how a government, hospital, bank or court is supposed to inspect, constrain or replace a model once it has entered critical workflows.
That question is no longer peripheral. The EU AI Act has moved compliance from abstraction to administration. NIST’s AI Risk Management Framework has given institutions a vocabulary for governing risk, even where law remains less prescriptive. OECD and UNESCO principles continue to shape the normative baseline. But principles and statutes do not implement themselves. They require interfaces. A right to explanation is empty without records. A requirement to test is shallow without agreed evaluation procedures. An obligation to monitor is difficult without telemetry that can be compared across vendors and contexts.
The surprising entry point, then, is not the frontier model but the connector. The future of AI governance will be decided in the technical and legal arrangements that determine how systems exchange information about provenance, performance, failure and authority. In the coming years, states may discover that they can tolerate dependence on foreign models more easily than dependence on foreign interfaces. Models can be swapped, fine-tuned or regulated at arm’s length. Interfaces, once embedded, are harder to dislodge because they organise entire ecosystems of tooling, auditing, procurement and professional practice.
From performance races to governability
The first phase of the AI boom rewarded raw capability. That era is not over, but it is being joined by another. As systems move into public administration, finance, health care, education and industrial operations, the central problem becomes governability. Can an institution know what was used, when, by whom and under which constraints. Can it compare outputs across versions. Can it reconstruct a decision pathway after an incident. Can it quarantine a component without breaking the rest of the workflow. These are not simply engineering concerns. They are the preconditions of liability, redress and public legitimacy.
Most organisations today still rely on arrangements that are too bespoke. One supplier offers one logging format, another exposes only limited audit data, a third treats evaluation as a confidential internal process. This may be commercially convenient, but it is institutionally corrosive. It fragments oversight and increases switching costs. It also makes independent assurance more theatrical than real, because auditors must spend disproportionate effort translating one system’s disclosures into another’s categories.
If the 2010s taught the world that platform power often resides in standards hidden beneath the user interface, the 2020s are teaching a similar lesson for AI. The technical artefact that matters most may not be the model card or the chatbot front end. It may be the machine-readable event log, the schema for incident reporting, the provenance tag attached to generated media or the benchmark definition that procurement officials quietly adopt across an entire sector.
The decisive standards battle is shifting from model architecture to the interfaces that make systems legible to institutions.
Why interfaces become political
It is tempting to treat interoperability as a merely technical virtue. In practice, it is a constitutional question for the digital state. Interfaces decide which actors can verify claims, which can integrate substitutes, which can inspect risk and which must accept opacity. They determine whether public agencies can exercise oversight directly or must rely on vendor attestation. They shape whether competition occurs on the merits or is blunted by lock-in disguised as convenience.
This is especially important in AI because risk is distributed across supply chains. A single deployed system may involve a foundation model, retrieval tools, fine-tuning datasets, content filters, identity services, cloud infrastructure, evaluation suites and user-facing applications. Responsibility is therefore easy to diffuse. When something goes wrong, each layer can claim partial visibility and limited control. Standardised interfaces are one of the few available mechanisms for making multi-layer accountability practical rather than rhetorical.
The geopolitics are equally sharp. Countries that do not set the rules for interfaces often inherit other people’s assumptions about evidence, safety thresholds, acceptable monitoring and access rights. In effect, they import not only software but administrative theory. That may be reasonable in some sectors. In others, it creates a mismatch between domestic law and operational reality. A state can pass rules on high-risk AI, but if the tools procured by its agencies cannot emit the records needed for verification, the law remains aspirational.
The rise of compliance plumbing
The decisive standards battle is shifting from model architecture to the interfaces that make systems legible to institutions.
One of the less glamorous consequences of the EU AI Act is that it has made compliance plumbing a strategic field. Conformity assessment, post-market monitoring, technical documentation and serious incident reporting all imply repeatable information flows. Similar dynamics are visible elsewhere through sectoral guidance, procurement standards and risk management frameworks. This does not produce immediate global convergence. It does, however, create pressure for common formats and shared vocabularies, because institutions cannot indefinitely absorb the cost of bespoke assurance for every system they buy.
Over time, the winners in this environment may not be those with the most impressive demonstrations, but those whose systems can fit into auditable chains of responsibility. This changes incentives. It favours modularity over mystique, documentation over improvisation and integration discipline over grand claims. It also gives standards bodies and public procurers an influence they have lacked in much of the consumer internet era. When a ministry, hospital network or critical infrastructure operator insists on exportable logs, standardised testing artefacts and clear update notices, it is not being bureaucratic. It is defending its capacity to govern.
There is a useful historical analogy in cyber security. For years, many organisations treated security as a product feature. Eventually they learned to think in terms of frameworks, controls, incident reporting and supply-chain assurance. AI is moving through a similar transition. The notable difference is that AI touches meaning and judgement, not only confidentiality and system integrity. Its governance therefore requires not just technical telemetry, but records that capture context, intent, human intervention and known limitations.
Three interfaces that will matter most
Not every protocol deserves strategic attention. Some are transitory, and some are best left to market experimentation. But three classes of interface are likely to prove foundational by the end of this decade.
Provenance and authenticity
As synthetic text, audio and video spread through administrative, commercial and political channels, provenance becomes basic civic infrastructure. The point is not to create a fantasy of perfect authenticity. It is to improve the odds that recipients can evaluate origin, transformation history and chain of custody. Standards work around content credentials and watermarking has exposed the difficulty of this task, especially under adversarial conditions. Even so, weak provenance is better than none, provided institutions avoid overstating what it can guarantee.
Evaluation and reporting
There is still no universal agreement on how to evaluate general-purpose AI systems across contexts. That is unlikely to change soon. Yet a more modest and more tractable goal is available: common reporting structures for what was tested, under which conditions, with which known exclusions, and how results changed after updates. Shared reporting does not eliminate methodological disputes. It makes them comparable. In policy terms, comparability is a large advance.
Operational control layers
The most sensitive deployments require controls around access, delegation, escalation and rollback. Who is authorised to invoke a system. Which tasks require human sign-off. How are exceptions handled. Can the system be degraded safely under stress. These questions point towards standardised policy layers rather than ad hoc prompts and dashboards. They are the difference between using AI as a tool and absorbing it as an unaccountable institutional habit.
A protocol is never merely technical; it decides who can participate, who can inspect and who must trust.
The hidden danger of elegant lock-in
Much vendor lock-in in enterprise software has been obvious. AI lock-in may arrive dressed as convenience. A model that plugs smoothly into document systems, communication tools and workflow software can become difficult to replace long before procurement teams realise how dependent they have become on proprietary monitoring, proprietary safety controls and proprietary retrieval formats. The more capable the system, the stronger the temptation to accept these surrounding constraints as a reasonable price for performance.
A protocol is never merely technical; it decides who can participate, who can inspect and who must trust.
This matters because lock-in weakens policy. If an agency cannot switch providers or independently inspect records without major operational disruption, regulatory leverage diminishes. The same is true for firms in concentrated sectors such as finance or pharmaceuticals. They may retain nominal bargaining power, but their practical room for manoeuvre narrows once surrounding tools, staff practices and assurance procedures become tailored to one ecosystem.
The answer is not autarky. It is interface discipline. Contracts, procurement frameworks and sectoral guidance should distinguish between proprietary innovation at the model layer and interoperability obligations at the control layer. In plain terms, suppliers can compete on capability while still being required to emit standard logs, support standard incident taxonomies and permit secure export of essential records. Such obligations are not anti-innovation. They are what prevents innovation from hardening into dependency.
Standards bodies will not be enough
Formal standards organisations matter, and their work will become more visible. ISO and IEC committees, sectoral regulators and national institutes all play important roles in creating common language and baseline procedures. Yet many of the operative standards in digital technology have historically emerged through procurement, open-source practice, industry consortia and de facto adoption rather than solely through classic standard-setting channels. AI will be no different.
This should temper both optimism and cynicism. Formal standards can be slow, but they confer legitimacy and durability. Informal standards can evolve quickly, but they often reflect the power of the actors already closest to deployment. The task for policymakers is therefore not to wait for a single definitive framework. It is to shape the market conditions under which provisional standards emerge, especially in sensitive sectors. Public procurement is one of the strongest instruments available because it converts abstract principles into operational requirements.
There is also a role for regulators in insisting that conformity evidence be portable. A useful standard is not only one that defines a metric. It is one that allows documentation, test results and incident records to move across tools and jurisdictions without prohibitive translation costs. Portability may sound pedestrian, but it is often the difference between oversight that scales and oversight that collapses under administrative burden.
The sovereignty question, properly understood
Talk of technological sovereignty is often too binary. Few countries will build a fully independent AI stack, and fewer still should try. The real question is where independence is essential, where interdependence is acceptable and where resilience requires substitutability. On that spectrum, interfaces deserve priority because they preserve room for national and institutional choice even in the presence of foreign dependencies.
A country might rely on imported semiconductors, foreign cloud providers and internationally developed models, yet still retain meaningful control if it can mandate auditable interfaces, local compliance artefacts, secure data handling and interoperable oversight tools. Conversely, a country may invest heavily in domestic champions and still discover that core governance functions depend on formats and control mechanisms designed elsewhere. Sovereignty, in other words, lies partly in the power to define how systems must present themselves to law.
This is why smaller states should not assume that the standards game belongs only to superpowers. In some domains, coalitions of regulators, public buyers and technical agencies can exert influence disproportionate to their size. Europe has demonstrated this repeatedly in privacy and digital regulation, though not without trade-offs. Other regions can do so through sector-specific coordination, mutual recognition regimes and shared procurement language that rewards interoperability rather than short-term customisation.
What good interface policy looks like
First, it is specific. General appeals to trustworthy AI are too vague to shape implementation. Better policy names the artefacts required for assurance: version histories, evaluation summaries, incident logs, provenance records, role-based access controls and update notifications.
Second, it is layered. High-risk systems need stricter interface obligations than low-risk consumer tools. The objective is not to burden every application equally, but to align reporting and control requirements with plausible harms and institutional dependence.
The countries that cannot influence interfaces may still buy AI, but they will struggle to govern it.
Third, it is portable. Evidence produced for one regulator, auditor or procurer should be reusable where legal contexts overlap. Redundant reporting drains attention from substantive risk management.
Fourth, it is adversarially aware. Provenance can be spoofed, logging can be incomplete, and metrics can be gamed. Standards must therefore support challenge and verification rather than resting on self-description alone.
Fifth, it is compatible with pluralism. Not every sector needs the same benchmark, ontology or workflow. The aim is coordinated diversity: enough common structure to enable comparison and accountability, enough flexibility to reflect domain realities.
The labour and institutional dimension
There is another reason interfaces matter: they shape how work is reorganised. Much discussion of AI and employment still focuses on task automation and productivity. Less attention is paid to the operational scripts through which institutions decide what staff may delegate, when they must review outputs and how they document responsibility. These scripts are, in effect, protocols for human-machine collaboration.
If badly designed, they either create false confidence or produce compliance theatre in which workers click through nominal review steps without meaningful oversight. If well designed, they clarify when AI acts as drafting aid, triage mechanism or decision support tool, and they preserve evidence of human judgement where it matters. This is essential not only for labour standards but for professional legitimacy in medicine, law, education and public service.
The deeper point is that standards do not only structure machines. They structure institutions. They influence who bears risk, who gains discretion and who gets blamed after failure. Any serious politics of AI must therefore treat protocol design as a workplace issue and a constitutional one, not merely an engineering detail.
A coming divergence: open capability, closed governance
One plausible future is that model capability becomes more widely available while governance interfaces become more concentrated. Open-weight and widely accessible systems may lower entry barriers at the capability layer, yet the surrounding compliance, monitoring and orchestration stack could remain tightly controlled by a smaller number of firms and jurisdictions. If that happens, apparent democratisation will coexist with practical dependence.
This scenario would confuse many current debates. Observers might note that models are abundant and infer that market power has weakened. In reality, the locus of power would have moved to the control plane: who defines acceptable telemetry, trusted identity, benchmark disclosures, provenance chains and policy enforcement hooks. The strategic mistake would be to celebrate openness at the model layer while neglecting closure at the interface layer.
The countries that cannot influence interfaces may still buy AI, but they will struggle to govern it.
The unglamorous frontier
The next few years will bring more spectacular models, more capable agents and more intense arguments about safety and competition. Yet the less visible frontier may prove more enduring. Societies do not govern powerful technologies through aspiration alone. They do so through records, schemas, audit trails, testing regimes and rights of access. They do so by deciding what a system must reveal about itself in order to be trusted with consequential tasks.
This is why standards and protocols deserve to move from the annex to the centre of AI policy. They are not decorative supplements to innovation. They are the means by which innovation becomes governable, contestable and, when necessary, replaceable. In an era fascinated by scale, the decisive power may lie in the seam.
