On June 2, the White House quietly published an executive order that almost no one in India will read closely, and that almost everyone in our public sector should. It puts in place an idea missing from every government's AI playbook so far: a sovereign capability to test frontier AI models before they touch the sensitive parts of the state.
The mechanism is unfussy. Within sixty days, the Director of the National Security Agency, in consultation with a handful of other officials, must develop and maintain a classified benchmarking process to assess the advanced cyber capabilities of AI models and determine the threshold at which an AI model should be designated a "covered frontier model". AI developers are invited, voluntarily, to hand a model to the federal government for up to thirty days before releasing it to anyone else. There is no licensing regime; the order expressly forbids one. But there is now a place where the state can look under the hood before the rest of the economy gets to drive the car.
The more interesting half of AI policy
India's AI conversation is loud about two things: compute and use cases. We talk about GPUs by the tens of thousands, about Bhashini, vernacular chatbots, AI in courts. Both matter. Neither answers the question every senior bureaucrat will face within the next three years.
That question goes like this. A vendor offers us a model that can read a citizen's tax history, draft a notice, recommend an action, and execute it. How do we decide whether this specific model is safe enough to be allowed into our environment? Right now, the honest answer is that we decide on vendor reputation, a procurement scorecard, and the judgment of two or three officers who have been around the file long enough to be trusted. That is not nothing. But it is not a state capability. It is hostage to the personalities and office life of the moment. And it does not scale to a country that runs DBT, GSTN, an income-tax stack, a new criminal procedure, and a thousand state-level applications on the same architectural assumptions.
What the order gets right
The good instinct is the separation between innovation and security. The order is loudly pro-innovation; it explicitly refuses to stifle the industry with regulation and rules out any mandatory licensing of new models. At the same time, the same document sets up an AI cybersecurity clearinghouse, expands a federal Tech Force, and asks CISA to make even covered frontier models accessible to operators of critical infrastructure such as rural hospitals, community banks, and local utilities.
It treats the question of whether a model is safe enough for sensitive deployment as separate from the question of whether it can be sold at all. That separation matters. Most jurisdictions, including ours, collapse these into one bucket called "AI regulation". The result is either over-regulation in the name of safety, or no real safety work at all because the political cost of the first option is too high. The American order suggests a third path: government as a privileged tester, not as a gatekeeper.
It leaves much open, too. A classified benchmark used only by NSA, with no public-sector analogue in the agencies that will actually deploy these models - health, tax, courts, energy - is incomplete. A thirty-day pre-release window is short. And the voluntary nature of the framework will work only if industry sees a clear benefit; the order hints at this through privileged early access for "trusted partners", but the carrot is not yet sharp.
An Indian version, sketched
The better view is that we should not wait. Three concrete moves I believe should be taken, none of which need new legislation.
A state-side model evaluation cell
House it within MeitY or CERT-In, staffed by a mix of officers and contracted technical talent on three-year tours. Its job is not to police the AI industry. Its job is to build benchmarks aimed at the failure modes that hurt government most: prompt injection in workflows that touch personal data, reasoning collapse under adversarial inputs in tax assessment, hallucinated citations in legal drafting or during chatbot functioning, model behaviour under translation between Indian languages. Publish what you can. Keep the rest classified. The point is to build a small group inside the state who, over time, develop instincts no procurement officer can substitute for.
A "fit for sensitive deployment" tag
Not a licence. A signal. A model that has been tested against the cell's benchmarks receives a tag that any department or any operator of critical infrastructure can default to when shortlisting vendors. Industry will adopt the tag because the customer base is large enough to make it worth the engineering.
A pre-deployment review for the highest-risk uses
For deployments that touch tax assessment, criminal procedure, biometric matching, grid SCADA, or welfare targeting or Enforcement Directorate for that matter, require a written review by the cell, the line department, and one external technical reviewer. Thirty days. Default approval if no issues are raised in writing. Reasons recorded either way. This is, ultimately, file work. File work is something the Indian state knows how to do.
The deeper point
The instinct, when a powerful new technology arrives, is to build an external regulator. The better move, more often than we admit, is to build internal capability. Having worked on AI systems that talk to ordinary citizens inside a national administration, I am convinced that what slows public-sector AI in India is not a missing regulator. It is the absence of trusted people inside the state who can look at a specific model and say, with reasons, whether it should be allowed near a citizen's record. We need Officers with AI bent.
The American order, in its limited way, has admitted as much. The interesting thing about June 2, 2026, is not the politics around it. It is the quiet acknowledgement that even in a country with the world's deepest pool of AI talent, the state still needs its own pair of eyes. We need ours sooner than we think.
#AIGovernance #FrontierAI #PublicSectorAI #IndiaAI #StateCapacity #AISafety #DigitalIndia
No comments:
Post a Comment