A Payroll Wedge Just Vanished

India's Comprehensive Economic and Trade Agreement with the United Kingdom enters into force today, and most of the coverage will lead with the 99 percent duty-free access on tariff lines. The more interesting instrument arrived beside it. The Double Contribution Convention exempts Indian professionals on temporary UK assignments (five years, extended from three) from paying into Britain's National Insurance while they continue to contribute at home. The report in India Briefing pegs the annual saving at roughly USD 500 million, covering 90 to 95 percent of Indian professionals sent through Indian employers. That number matters less than the frame. India's largest single export is not steel or leather; it is people-hours priced in foreign currency. Tariff talk fixates on goods, but the real friction in services trade has always been a payroll wedge: mandatory contributions the visiting worker never gets to draw down. Neutralising that wedge inside a trade treaty is a subtler innovation than any tariff schedule, and probably a more durable one. The next FTA worth watching is the one that repeats this move.

#CETA #IndiaUKTrade #DCC #ServicesTrade #FreeTradeAgreement #GlobalMobility #SocialSecurity

The Line Above Four

India's June CPI print landed at 4.38%. It sounds unremarkable. It is not. That is the first time in seventeen months the number has crossed the RBI's four percent target, as recorded in a Bloomberg report on Monday. The reading stayed inside the tolerance band. But a line was quietly crossed, and lines matter in monetary policy the way statute matters in tax administration: not because breaking them is catastrophic, but because they change the standard of proof.

The RBI cut 125 basis points last year and pushed liquidity into the banking system on a scale that would have been unusual in a tighter era. The private capital cycle was supposed to receive that liquidity and put it to work. Then food happened. Nearly forty percent of the consumer basket in India is food, and this year's monsoon has run below normal. The government's own Monthly Economic Review argues the economy is now less exposed to rainfall than before, and that is broadly true in the aggregate. But the price index does not measure the aggregate. It measures households in their kitchens.

From inside a national tax administration, one learns that macro forecasts and taxpayer reality diverge more than models suggest. TDS collections track nominal transactions. Nominal transactions carry inflation inside them. Every basis point of CPI drift shows up months later in the shape of the tax base, in the composition of refunds, and in the arguments taxpayers make about real versus nominal incomes. Inflation is not just a monetary story. With a lag, it becomes a tax administration story too.

The immediate temptation, when a target line is crossed, is to over-read the print. One month is a data point, not a trend. But the WPI figure released the same week printed close to its three-year high. Two indices, drifting apart, telling different stories about the same economy. Wholesale is a producer's world; retail is a consumer's. When they diverge this widely, the middle layer of small firms, informal wage earners and first-year borrowers absorbs the friction.

The takeaway is not for the RBI. They will do what the numbers oblige them to do. The takeaway is for anyone building fiscal, tax or investment plans for the second half of this year. Assume a firmer floor under prices, and design for it now, quietly, before it becomes fashionable to do so.

#IndiaEconomy #Inflation #RBI #MonetaryPolicy #CPI #WPI #TaxPolicy #FiscalPolicy

One Screen, Two Statutes

A small notice on the e-Filing portal this week is worth pausing on. The department has quietly rolled out an integrated payment module that lets taxpayers pay dues under the Income-tax Act, 1961 for periods up to FY 2025-26 and under the Income-tax Act, 2025 for Tax Year 2026-27 onwards, all from a single interface. The notice on the Income Tax Department portal puts it plainly:

Seamless payments now enabled across both the Income-tax Act, 1961 and the Income-tax Act, 2025.

That word, seamless, does a lot of work. India is running two direct tax statutes in parallel, one for closing out old years and one for opening new ones. Every legal transition of this scale creates a temptation to make the citizen learn the transition too, to force them to pick which Act their payment belongs to, to route them through different portals, different challan formats, different mental models. The interesting bit of engineering here is the opposite instinct: absorb the complexity inside the system so that a person paying a demand from AY 2022-23 and a person paying advance tax for TY 2026-27 use the same three clicks. The citizen does not need to know which statute is doing the arithmetic.

There is a wider lesson for public administration in this. The measure of a good transition is how quickly it becomes invisible to the person on the other side of the counter. Officers see two Acts, two sets of rules, two saving clauses, two mental frameworks running simultaneously. The taxpayer should ideally see one screen. That gap, between the complexity we carry internally and the simplicity we present externally, is where administrative craft lives. It is worth building for. And it is worth defending against every impulse to expose the plumbing.

#IncomeTax #IncomeTaxAct2025 #CBDT #TaxAdministration #DigitalIndia #eFiling #TaxReform

UPI Prepares For Machine Users

Between the noise of frontier model releases and the ITR filing rush, a quieter Indian move this week deserves more attention. According to a report in Business Standard, NPCI is working on a Unified Agent Protocol so that AI agents can, with the user's permission, make payments over UPI. The plumbing is being drawn now, in consultation with the industry, and it will need RBI clearance before it goes live.

This is not a small feature. It changes who the "user" of a national payments rail is. For eighteen years of digital India, the working assumption has been one human, one device, one intention per transaction. UAP contemplates a different assumption: a piece of software acting on your behalf, initiating value transfers between banks, at speed, at scale, and often when you are asleep.

The rail, not the app, is the state's job

The instinct in newsroom coverage is to ask which AI assistant will pay first, which quick-commerce platform will move first, which bank will onboard first. That framing misses the point. The private sector will produce the agents. But agents cannot talk to a payments system unless someone builds a shared, trusted way of introducing them, verifying them, and revoking them when they misbehave. That is a public infrastructure question, not a product question.

The same reporting notes that Visa is building a Trusted Agent Protocol, Google has an Agent Payments Protocol, OpenAI has an Agentic Commerce Protocol, and Pine Labs has P3P. Each of these is a private schema competing for adoption. India's answer is different in shape: a common protocol, sitting above private agents but below the bank rails, run by a body that already coordinates the industry. That shape difference matters more than the technical details.

Why a state adjacent register is the right answer

An AI agent that moves money on your behalf is, in effect, a narrow private power of attorney executed at machine speed. The three questions the law has always asked about such powers are unchanged. Is the delegate real? What is the scope? What happens when scope is exceeded? UAP appears to want answers to all three: a registry, an authorisation envelope with spending limits, and audit logs that allow a payment to be reconstructed after the fact. None of these can be credibly provided by any one of the competing private schemas, because their commercial incentives run in the other direction.

What this means for tax and compliance

From inside a large tax administration, the second order effects here are more interesting than the first order ones. Consider three.

Attribution of transactions

Every agentic payment is a transaction the user initiated in intention but not in execution. Tax law has thin machinery for that distinction. When your agent buys a cross border subscription, or repeatedly tops up a wallet, the audit trail must show that the human principal, not the agent, is the taxable person. A registry of agents, plus a log of who authorised which agent to spend how much within what window, is exactly the primary evidence a revenue officer will one day want. UAP, incidentally, is building that evidence layer.

Fraud patterns will migrate

Every payments innovation is followed by a fraud innovation. UPI's own history is proof. When agents start executing recurring low value purchases, the fraud will not be brute impersonation of the human. It will be quiet capture of the agent, either by compromising the credential or by prompt level manipulation of what the agent decides to buy. Rules that ask only whether the payment was authorised will not catch this. The real question becomes whether the decision the agent took was one the user would have taken. That is a new class of dispute, and the consumer protection frameworks around UPI will have to grow into it.

The invoice, the payment log, the return

If a routine grocery order is executed by an agent that also holds the user's GSTIN and preferences, the natural next step is that the invoice, the payment log, and the return pre-fill start speaking to each other automatically. Tax administrations everywhere have been talking about pre-filled returns for a decade. Agentic commerce is what finally forces pre-fill to become the default rather than the exception.

What a tax department should be doing this quarter

Two things, quietly.

First, seat someone in the room during UAP design. Not to slow it down, but to make sure the log schema captures the fields a revenue authority will one day need: agent identity, principal identity, spend envelope, timestamp, merchant category, and the human confirmation trace. Retrofitting those fields later is always more expensive than agreeing them now.

Second, begin scenario work on what pre-filled returns look like when the underlying spend is agent initiated. Category assignment, personal versus business use, and the taxpayer's ability to challenge an entry generated by software the taxpayer barely understands. These are not futuristic problems. If UAP moves at UPI speed, they arrive within three assessment cycles.

India tends to build payment rails first and think about their tax and legal downstream later. UPI is itself the case study. There is a narrow, useful window here to do it the other way round.

#UPI #NPCI #AgenticAI #DigitalPayments #IndiaAI #PublicInfrastructure #TaxAdmin #UAP

Plain English Is The New API

Reston, Virginia. On 7 July, an American technology firm called Peraton launched what it billed as the first true enterprise agentic AI platform for government operations. In the report in NextGen Defense, the description of the tool is deceptively simple:

Users can query the system in plain English to identify project risks, monitor progress, and gain real-time insights.

I read that sentence twice. Not for the marketing gloss, but for the quiet implication buried in it.

For three decades the story of government IT has run the same script. Buy an enterprise system, spend two years customising it, train a small priesthood of operators, live with the quirks for a decade because migration is unaffordable. The bottleneck was never data. It was the specialist layer between the user and the data. Any officer who has ever needed a report from a legacy application and been told we will raise a ticket knows this bottleneck in her bones.

If the plain-English promise even half holds, that layer starts to thin. A field officer who wants to see all pending appeals in one district by tax head, or the desk officer tracking anomalous refund patterns this quarter, would ask the system directly. No ticket, no intermediary, no six-week wait.

The catch, and it is a serious one, is traceability. In administration, the model said so is not a defensible answer. Every output that touches a decision must tie back to a rule, a return, a scrutiny note. Vendors are already promising this loudly. Governments will have to test it just as loudly, on their own data, in their own languages, with adversarial cases picked by their own auditors.

A modest proposal for any large Indian department contemplating agentic AI. Insist on three non-negotiables inside the procurement itself. First, an offline sandbox on real, redacted departmental data before any commitment is signed. Second, a written explanation for every query result, citing the source records. Third, a full audit log that a Comptroller can read a year later without help from the vendor.

The novelty here is not the model. It is the interface. When plain English becomes the query language, the constituency for institutional data widens from the few hundred people who know the schema to every officer with a question. That is either a productivity revolution or a governance nightmare, depending entirely on how quietly the audit trail is built.

#AgenticAI #PublicSectorAI #GovTech #IndiaGovernance #DigitalGovernment #TaxAdministration #AIProcurement

The Tech Cycle Is A Buffer

The International Monetary Fund's July World Economic Outlook Update, released on 8 July, kept the headline forecast almost unchanged: global growth of 3.0 percent in 2026, 3.4 percent in 2027. India's 2026 number was trimmed by a tenth of a point to 6.4 percent, while 2027 was raised by two tenths. The narrative is the interesting part. The Fund now frames the world through two opposing forces, one of which is the accelerating global technology cycle.

Buried in the tables sits a striking figure. The top four net exporters of AI hardware posted a first quarter growth surprise of 4.4 percentage points; the rest of the world came in at minus 0.3. That is not noise, and it is not one quarter's story. The Fund is candid about the mechanism.

Economies plugged into the technology-led upturn experience stronger activity even if they are energy importers.

A new axis is being drawn across the world map, and it does not run along oil. India sits in an unusual place on that axis. We are a large energy importer, exposed to the Strait of Hormuz on any given morning, yet we are also deep in the technology value chain and getting deeper. That is why the 2026 dip is small and the 2027 line ticks up.

The uncomfortable implication for policy is concrete. Insulation from an oil shock is no longer only a strategic reserve problem or a subsidy problem; it is now a value chain problem. Every rupee that pushes India further into chips, foundation models, and applied AI is, in effect, an energy buffer. Falling behind the cycle would make the next barrel hurt more than the last one did.

#IMF #WorldEconomicOutlook #IndiaGrowth #AIeconomy #TechCycle #EnergyShocks #Macroeconomics

Two Winds Move The Market

The IMF's July 2026 World Economic Outlook Update landed today with a line that reads like a whole thesis compressed into eighteen words: the WEO Update from the IMF describes global growth as "steady but uneven across countries amid headwinds from the war and tailwinds from the technology upcycle". That is the map. Oil chokepoints, semiconductor concentration, and AI capex are no longer separate stories; they are one story about which wind blows harder each morning. For anyone watching capital flows from inside a tax administration, this composition matters more than the headline number. When growth is powered by a narrow tech cohort and drained by an energy shock elsewhere, revenue is thin at the base and thick at the top, and the fiscal system inherits that shape. India's advantage, if we play it well, is that both winds cross this coast. The question is whether we build sails or shutters.

#IMF #WEO #GlobalEconomy #Markets #Geopolitics #AICapex #IndiaEconomy #FiscalPolicy

Close Small Loops First

If you have just left campus and are looking for your first job, or you are three weeks into one and unsure of what to do with yourself, this note is for you.

Everyone will tell you to network, to build a personal brand, to learn AI, to move fast. Some of that will help. Most of it will not, at least not yet. Here is the one thing that has quietly separated the people I have watched grow from the people who did not: they finished small things all the way.

The world is full of clever starters. You can spot them in any office. They arrive with three ideas on day one, four on day two, and by the second month they are already restless about their next role. They pitch, they suggest, they draft, and then they drift. Their calendar is full and their record is thin. They mistake motion for progress and slides for outcomes.

The people who become leaders in their first two years look almost dull in comparison. They pick one small problem, often something no one asked them to fix, something everyone quietly complains about, and they close it. They do the unglamorous last twenty percent that most of us duck. They write the follow-up email. They chase the missing signature. They send the file. They keep the tracker updated. They come back the next week and ask if it actually worked.

That is where trust begins. In any serious organisation, and especially in a large public institution, senior people are drowning in unfinished threads. Someone who reliably closes loops becomes precious very quickly. You do not need seniority for that. You need patience and follow through. Both are learnable and neither requires permission.

So here is the practical ask. In your first six months, pick one small thing that annoys your team and quietly fix it. Not a strategy. Not a deck. A workflow, a checklist, a template, a broken link, a slow approval, a missing reminder. Finish it end to end. Then pick the next one. Do not talk about it much; let people notice.

You will learn more about leadership from closing five small loops than from any book on the subject. And when your first real assignment arrives, and it will, you will already have the one habit that separates people who lead from people who merely start.

#leadership #careeradvice #firstjob #graduates #followthrough #newprofessionals #careers

Refunds Are Where Trust Lives

Somewhere in Bengaluru, at the Centralised Processing Centre, roughly twenty-seven lakh income tax returns crossed the ninety-day mark this year without a refund being released. That figure surfaced quietly in the thirtieth report of the Parliamentary Standing Committee on Finance, alongside a much larger and older number: outstanding direct tax arrears of Rs 47.42 lakh crore. Both numbers, read together, describe the same underlying question. How much friction can a modern tax administration absorb before the citizen starts noticing?

The most watched interaction is the refund

For most Indians who file a return, the refund is the entire relationship with the tax department. Assessment, penalty, appeal: these belong to a tiny minority. The refund does not. It is the one moment every year when a citizen looks at the state and asks whether her money is coming back. When that moment slips from thirty days to ninety, and from ninety to something no one is quite willing to publish, a small quiet trust erodes. Not dramatically. Just steadily.

According to the report in CAclubindia, the panel acknowledged the cause plainly:

"partly due to intensified verification measures introduced by the Income Tax Department to detect fraudulent deduction claims."

That is a real reason. It is also not the whole reason.

Scrutiny got smarter, but also wider

Third party data has grown faster than trust in it

The AIS, the expanded 26AS, the NUDGE nudges, the section wise risk flags: all of these were built to give the department eyes it never had. The eyes work. But every extra data field also becomes an extra mismatch, an extra flag, an extra manual look. Fraud detection scales up, but so does false positive burden. A refund that would once have moved in three weeks now waits for a person to look at a screen and confirm that a Section 80G donation actually happened.

Volume did not shrink; scrutiny only widened

Filings for the last assessment year crossed 8.8 crore. The verification net widened while the queue kept lengthening. When you tighten a filter on a river that is getting fuller, the river does not slow down. It backs up.

The delay is not free for the exchequer either

Section 244A quietly meters the cost

Every rupee of refund that misses its window earns interest at half a per cent a month for the taxpayer. The government is right to check claims. But every additional day it holds an honest refund, it also holds an accruing liability. Twenty seven lakh honest cases is not a rounding error. It is a compounding one.

The arrears mirror explains something too

The 47.42 lakh crore of outstanding direct tax demand is not a symmetric problem. Much of it is old, contested, or, as the department itself concedes, largely unrecoverable. The lesson is uncomfortable. The system has become very good at generating additions and very slow at closing loops, whether the loop is a refund or a demand. Both sides of the ledger are getting longer.

Three moves worth making now

Tier the scrutiny, not the taxpayer

Not every refund needs the same lens. A pensioner claiming standard deduction and a first year filer claiming a large HRA against a small salary do not sit in the same risk band. Risk band routing, published as policy, would let the vast majority of small refunds flow without a human blink, and concentrate assessors where the money actually is.

Publish a service standard, and pay against it

The department already has an internal ninety day norm. Make it external and measurable. If a refund slips past that line without a defensible risk flag, Section 244A interest should be treated inside the system as a real cost, not an accounting entry. Nothing focuses an organisation like a metered price on delay.

Report the trust cost the way we report the fraud saved

Every year, the department publishes fraud detected and revenue protected. Both are legitimate metrics. Neither is complete without its twin: honest refunds delayed, and days lost per honest filer. Institutional productivity, as any serious student of public sector organisation will insist, requires measuring what you break as carefully as what you build.

The quiet takeaway

Twenty seven lakh delayed refunds is not a scandal. It is a signal. It tells us that the country's largest revenue machine has grown a new muscle, faster detection, without yet growing the reflex, faster release. The fix is not to lower the guard. It is to sequence the guard. A tax system is not judged only by the fraud it catches. It is judged by the honest citizen who filed early, matched every number, and is still refreshing a portal in July.

#IncomeTax #TaxAdmin #CBDT #RefundDelay #PublicSector #TaxPolicy #India

Tariffs Now Speak Statute

The proposed 12.5% additional duty on Indian goods under Section 301 is not the loud, headline tariff of the past year. It is quieter, drier, and more dangerous. When the US Supreme Court struck down the sweeping emergency powers tariffs in February, the response was not to abandon protectionism. It was to relaunch it inside a statute that has withstood judicial review for half a century. Section 301 requires a formal investigation, a written record, a hearing. It rewards preparation, not outrage.

India's response, which will be tested at the USTR hearing next week, is precisely the right one on paper. According to the report in The Tribune, officials will argue that the findings on forced labour are legally flawed and that the duty would hurt American consumers as much as Indian exporters. The written case rests on Article 23 of the Constitution, the Bonded Labour System (Abolition) Act, the four Labour Codes, and India's ratification of the core ILO conventions. This is not diplomacy. It is comparative statutory law.

The strategic point sits underneath the immediate hearing. Trade action, for the next several years, will not travel through tweets or emergency proclamations. It will travel through Section 301 investigations, Section 232 national security findings, Section 122 balance of payments surcharges, and forced labour import bans. Each is a legal instrument with a docket, a record, a review. A country defends against such actions not with press statements but with the seriousness and precision of a legal brief. Export competitiveness will increasingly be won or lost inside comment windows, hearing rooms, and cross examinations. The administrations that build that institutional muscle now, staffed with trade lawyers, economists, and career administrators who read American statute as fluently as their own, will not lose market access to litigation they never showed up for.

#Section301 #ForcedLabor #TradePolicy #IndiaUSTrade #Tariffs #USTR #TradeLaw #GlobalTrade

The AI Trade Widens Its Base

The Russell 2000, America's small-cap index, closed the first half of 2026 up more than 20 percent, its strongest first six months since 1991. The S&P 500 rose about 7.5 percent over the same stretch. Small caps are outrunning the top of the market by the widest half-year margin since 2003.

The interesting part is what pulled them up. Per the report in The Motley Fool, this is not a classic cyclical revival. It is a valuation catch-up on one side, and on the other, the AI trade finally reaching smaller companies. Consensus 2026 earnings growth for the Russell 2000 has climbed from about 23 percent at the start of the year to 38 percent, mostly through semiconductor and semiconductor-equipment suppliers pulled in by the AI build-out.

There is a familiar shape here. In a real technology cycle, the earliest returns concentrate in a handful of household names. Then, if the technology is genuine, spending moves down the capital stack: the tooling, the testing, the specialty inputs, the fabrication. The market notices that second wave later than the first, and rewards it more quietly. The 1990s ran this play. The current one appears to be running it again, only faster.

The read-across for a country hoping to be an AI producer, and not only an AI consumer, is uncomfortable. Indian policy conversations have concentrated on the visible surface of the stack: sovereign models, applications, chatbots. The value tends to accrete a few layers below that, in the suppliers, fabricators, calibration and testing houses that a small-cap index quietly represents. That is where American reindustrialisation is picking up an unglamorous second wind. It is also where our own listed universe has almost nothing to show at scale.

One caution. Bank of America estimates that every additional 25 basis point rate hike trims about 2 percent from Russell 2000 operating earnings, because small firms carry more floating rate debt than their large-cap peers. The Federal Reserve meets on July 28 and 29. That decision will matter more to the base of this market than to any name in the Magnificent Seven.

If you want to know whether an AI cycle is real, do not watch the biggest names. Watch the middle.

#Markets #Russell2000 #AITrade #SmallCaps #FederalReserve #IndiaEconomy #CapitalCycle #Semiconductors

Fair Is The Harder Half

The OECD released its 2026 Trust Survey this week, and buried inside is a finding that ought to reshape how any government department talks about its AI rollouts. Across 33 countries and five accession candidates, people are more optimistic that AI in the public sector will improve service quality and efficiency than they are that it will be fair, transparent, or protective of their personal data. Confidence sits close to four in ten on tailored services and cost reduction. It falls further when the question turns to fairness, human oversight, and the safety of the data citizens have already handed over.

Read the chapter in the OECD report and the shape of the trust problem is unmistakable.

Most people remain sceptical of AI deployed in the public sector.

That is the exact reverse of what a public administrator would prefer. In any tax office, in any welfare office, in any subsidy pipeline, citizens already assume speed as their due. The moment a refund lands one day faster, it becomes the new baseline. Trust is not accumulated at the efficiency edge. It is built, or lost, at the edges of fairness, of explainability, and of what happens to the record a citizen was legally required to file.

Which suggests the standard sales pitch for public sector AI is upside down. Enterprise AI has to prove return on investment. Government AI has to prove its accountability spine first, and the return on investment follows. Every deployment should surface its human reviewer, its audit trail, and its grievance route as visible product features, not as buried compliance. Otherwise each new efficiency claim widens the very gap the survey has just measured. Fast was always going to be the easy half. Fair is the one we still have to ship.

#AIGovernance #PublicSectorAI #GovTech #DigitalTrust #OECD #AIinGovernment #Accountability #TaxAdmin

Japan's Long End Wakes Up

On the last day of June, Japan's 30-year bond yield touched 3.95 percent while the yen sat at a four-decade low against the dollar, a move Bloomberg tied to Prime Minister Sanae Takaichi's fresh spending plans and the sense that Tokyo's debt-reduction drive has stalled. For a generation, Japan looked like proof that fiscal orthodoxy was optional: deficits could keep expanding, government debt could cross 250 percent of GDP, and the ten-year barely stirred, because the Bank of Japan owned so much of the market that price discovery had gone quiet. That silence is ending. As the BOJ steps back, long-end yields are re-learning what sovereign risk actually feels like, and the currency is doing the rest of the talking. The signal for every finance ministry watching, India's included, is not new but suddenly sharp: bond markets are patient, and then they are not. A tax base that broadens quietly, year after year, is not a technocratic virtue. It is the buffer that keeps yields from doing your policy for you.

#JGBs #JapanEconomy #SovereignDebt #BondYields #FiscalPolicy #BankOfJapan #Takaichi #MacroPolicy

The Return Now Argues With Data

As July arrives, so does the annual ritual of the income tax filing season. BusinessToday’s calendar for the month lists the familiar checkpoints: TDS deposits on the seventh, certificates and statements through the fifteenth, ITR-1 and ITR-2 due on the thirty-first. The deadlines look the same as last year. The system behind them does not.

About 27 lakh refunds for FY 2025-26 crossed the 90-day window last year. Not because the Centralised Processing Centre slowed down, but because returns no longer move through it in a single pass. Each one is now reconciled, line by line, against the Annual Information Statement, Form 26AS, TDS records, and disclosures already flowing in from banks, mutual funds and stock exchanges. A small mismatch in interest income or a stray capital gain is enough to push a return out of the straight-through queue. The verification is no longer human. It is data calling data.

This is a quiet but important reframing of what filing now means. The taxpayer is no longer reporting income to a department that knows nothing about it; the department already knows. The return is, in effect, the taxpayer’s hypothesis about what the consolidated record says she earned. If the hypothesis matches, money moves in a week. If it does not, a slow conversation begins between her form and the data trail behind her PAN. The lesson for this season is about posture. Open the AIS before opening the ITR utility. Treat the return as an argument with evidence already in the room. The safest filer this July is the one who treats the AIS as the document the return must agree with.

#IncomeTax #ITR #AIS #TaxAdministration #IndiaTax #TaxYear2026 #CBDT #Form26AS

Sovereign AI, Made Elsewhere

A small notice went out from Brasília on Friday and was made public yesterday. SERPRO, the federal technology company that holds the data spine of the Brazilian state, has chosen its partner for "IA Soberana", Brazil's national sovereign AI programme. According to the announcement carried by PR Newswire, the winner is MeetKai Brasil, the local arm of a Los Angeles company. Brazil's broader AI plan envisions roughly R$23 billion through 2028, large language models trained in Portuguese, all of it running on Brazilian infrastructure.

It is worth pausing on what sovereign means here. The vendor is foreign. The weights, the operating control, the data, the language of the model: all of these will sit inside Brazil. Sovereignty has been defined not as "we built it ourselves" but as "we hold the keys, in our language, on our soil". A country with a serious public data estate decided that the architecture of control matters more than the nationality of the builder.

For anyone watching India's own AI conversation closely, this is a useful distinction to import. Sovereign AI is not one thing. It is a stack with at least six layers: data, compute, foundation model weights, fine-tuning, hosting, governance. A government has to decide, layer by layer, which it must own, which it can lease, and which it should regulate without ever touching. Owning everything is expensive and slow. Owning nothing is a different kind of dependence. The hard work sits in the middle.

What India has done well, through a decade of digital public infrastructure, is own the rails: identity, payments, consent. What it has not yet decided, in public, is how much of the model layer above those rails should be Indian by ownership rather than Indian by use. The Brazilian tender is a quiet reminder that the answer need not be all or nothing. It can be this: we will host it, we will train it on our languages and our case files, and we will fire the vendor if they misbehave. That is a thinner sovereignty than the slogan, but it travels further.

The next time "sovereign AI" comes up in an Indian conference room, the right first question is not who built it. It is which layer of the stack you mean.

#SovereignAI #AIPolicy #PublicSector #IASoberana #DigitalSovereignty #IndiaAI #AIGovernance #DPI

AI Just Became Capital Risk

On 24 June, the Reserve Bank of India dropped a draft that does not look like an AI regulation at first read. It is titled Guidance on Regulatory Principles for Model Risk Management, 2026, and the language is pure prudential supervision: board-approved frameworks, three lines of defence, independent validation, risk tiering, model inventories retained for ten years after decommissioning. Spend twenty minutes with it and a sharper thought lands. India's central bank has just pulled AI into the family of supervisory tools normally reserved for capital and liquidity. The principle that a regulated entity remains fully accountable for the outcomes of every model it uses, including those sourced from third-party vendors, quietly closes a loophole that the entire fintech-banking AI stack had been leaning on.

What the draft actually says

The reach is wide. Eleven categories of regulated entities — commercial banks, small finance and payments banks, urban and rural co-operatives, NBFCs across all layers, AIFIs, ARCs, credit information companies — are inside the perimeter. The definition of “model” is wider still. It covers not just neural networks and generative AI but also algorithms, analytics tools, decision rules, even spreadsheet-based tools where they materially influence credit, pricing or risk decisions. Every such model must sit under a Board-approved Model Risk Management Framework. Every high-risk model must be cleared by the Risk Management Committee of the Board before deployment. Every customer-facing AI interface must disclose that it is AI, list its limitations, and offer the user a way to switch to a human. And every deployed AI system needs a working kill switch — a one-button deactivation if the outputs go wrong. Comments are invited until 24 July.

The deep idea: models as a new line on the risk ledger

This is the consequential part, and most early commentary is missing it. When a regulator says you cannot offload accountability to a vendor's API, it is doing for AI what Basel did for credit risk in the early 1990s. Models become a class of exposure. They have to be inventoried, tiered by materiality, validated independently, monitored for drift, and signed off at the highest level. That is the grammar of capital, not the grammar of code.

It is also the only grammar that scales. The RBI's own FREE-AI Committee survey last year found that nearly 21% of regulated entities were already deploying AI in production — across credit underwriting, cybersecurity, customer support, sales — and 67% wanted to go deeper. At that level of penetration, telling boards “your tech team has this” is not serious supervision. Every credit cycle eventually meets its model failure mode. A regulator that waits to discover the failure is a regulator already too late.

The kill switch rewrites the vendor market

Look at the supply side and the picture sharpens. A small set of global tech firms quietly supplies a disproportionate share of the AI models running inside Indian financial services. The draft flags this concentration explicitly as a systemic supply-chain risk. Combine it with the third-party-is-no-defence clause and the direction of travel is unmistakable: a serious push toward indigenous, auditable, swap-out-able model stacks. The new market is not the bank's market. It is a RegTech market — model validation firms, bias-testing labs, explainability auditors, red-teaming shops. A compliance officer reading this draft on Monday morning is realising that the next critical hire is not another data scientist; it is an independent validator who can sign off on someone else's data scientist.

Why this logic will travel beyond banking

I have spent enough time inside a national administration deploying AI on citizen-facing systems to read this draft as a template, not an end-point. Tax, customs, social security, urban service delivery, public health records — every government body running models on millions of files faces the same accountability question the RBI is now putting to banks. Who signs off on the model that decides a refund? A scrutiny notice? An eligibility threshold? The answer cannot be “the algorithm”. It has to be a named human, with a department behind them, with an institutional framework above them.

Three things from this draft will, I think, become the standard public-sector discipline within two budget cycles:

• the inventory rule — every active and decommissioned model on a register, with a ten-year tail;
• the explainability threshold — outputs interpretable to the extent the business process actually requires;
• the kill switch as a non-negotiable product feature, not a nice-to-have.

The trade-off, and the right side of it

The cost is real. Industry analysts already estimate a 50 to 100 basis point rise in IT spending for serious adopters. Smaller NBFCs and co-operative banks will feel it the most. Time-to-market for AI-driven products will lengthen. None of this is free, and the smaller institutions will need a transition window the draft does not yet promise.

But picture the alternative. A black-box model, bought from a vendor, denying loans to a cluster of small borrowers in a particular district, operating under no one's clear authority. Someone eventually discovers it — they always do. The regulator pays, the bank pays, the customer pays, and trust in AI itself pays the heaviest tax of all. The cost of the RBI's draft is the cost of preventing that discovery.

The cleaner way to say it: in a regulated industry, AI stops being a technology decision and becomes a capital decision. Capital decisions are made in boardrooms, not in model repositories. The window closes on 24 July. The more interesting question is not whether this framework is right for finance — it broadly is — but how quickly the rest of the public-private edge of AI adoption catches up. The RBI has, almost without saying so, written the first chapter of an Indian AI accountability code. Other regulators will write the rest, or they will inherit the failures of not having done so.

#RBI #AIGovernance #ModelRisk #BankingRegulation #IndianEconomy #AIAccountability #PublicFinance #RegTech

Korea Was The Canary

On Tuesday, June 23, South Korea's KOSPI fell 9.99 percent in a single session, tripping circuit breakers, wiping out roughly $2.5 billion in foreign capital in hours, and qualifying as the fifth-largest single-day decline in the index's history. Samsung and SK Hynix each lost more than twelve percent. The Nasdaq followed down 2.21 percent the next session. Oracle, in the same news cycle, disclosed it had cut twenty-one thousand jobs in a year — almost thirteen percent of its workforce — and named AI as the reason. Forty-eight hours, three disclosures. None of this is a tech story. It is the beginning of a macro story we have not yet learned to read.

The capex has become the commodity

For two decades we taught ourselves that crude was the single variable that synchronised global cycles. A spike in oil touched everything: inflation in importers, fiscal space in exporters, central bank reaction functions everywhere. That intuition is still half right. But a new variable has joined it, and the last week suggests it is, in the short run, more potent.

Meta, Google, Microsoft, Amazon and Oracle are between them committing capex plans this year that could touch seven hundred billion dollars to build AI data centres. Oracle alone reported negative free cash flow of $23.7 billion last fiscal year while raising capex 162 percent to $55.7 billion. Those numbers are not technology numbers anymore. They are macroeconomic numbers — comparable in scale to the annual oil import bills of mid-sized economies — and they are decided in a handful of US boardrooms.

This is the kind of single-factor dependence Professor Richard Robb's International Capital Markets course at Columbia kept circling: when cross-border flows are tethered to a small set of decisions on a small set of US balance sheets, the receiving economies inherit volatility they did not choose and cannot hedge. Korea just lived through one rehearsal.

Why Korea fell first

Korea was not a random victim. The KOSPI was up roughly 95 percent year-to-date going into Tuesday. Samsung and SK Hynix together account for about half the index by market capitalisation. The Bank of Korea has openly said AI-related chip exports will add 0.7 percentage points to 2026 growth, more than offsetting the drag from costlier oil. Taiwan is on track for 9.6 percent GDP growth this year — its highest in sixteen — on the same trade.

When the global market began doubting whether US hyperscaler capex was sustainable, every one of those exposures got marked at once. Three triggers converged on the same morning: MSCI again excluded Korea from its developed-markets watchlist, regulators raised flags about leveraged single-stock ETFs tied to Samsung and SK Hynix, and a hawkish Federal Reserve dot-plot from June 17 was already in the bloodstream. The market did not need a new fact. It needed a coordination point.

India's awkward middle position

India's place in this story is uncomfortable. Unlike Korea or Taiwan, India is not a meaningful seller into the AI hardware stack. Unlike China, it is not building frontier models at scale. The result is the worst of both worlds: when AI capex booms, India captures little of the upside; when it wobbles, the contagion still arrives — through portfolio outflows, currency pressure and the generic risk-off impulse against emerging markets.

The numbers this month are blunt. Foreign portfolio investors pulled roughly sixty-four thousand crore rupees out of Indian equities in the first half of June alone, the heaviest exit since March, with elevated oil and "concerns over AI's impact on tech revenues" cited as the principal reasons. Two macro factors, neither of which India controls, set the direction of an enormous slice of market cap. That is not market accident; that is structural exposure.

What policymakers should actually do

One. AI capex belongs on the macroprudential dashboard. The Reserve Bank's Financial Stability Report already tracks crude, dollar moves, FII positioning and banking-sector stress. It should now also track the announced capex plans of the five US hyperscalers, because in any given quarter those plans are a bigger swing factor for emerging Asia than the OPEC+ communique. Treating this as a tech-sector story is a category error.

Two. The export-services tax base — IT, ITES, global capability centres — is more cyclically exposed to AI capex than its standard sector classification implies. Revenue projections and advance-tax assumptions should stress-test against a fifteen to twenty percent compression in this base, not as a tail risk but as a plausible scenario for the coming eighteen months. A tax administration cannot afford to be the last institution to learn that a sector's cycle has changed.

Three. The Indian debate around "missing the AI boat" oscillates uselessly between buying chips and drafting strategies. The better path runs through demand the country actually controls — large-scale public-sector AI deployment in tax, courts, health, urban services — so that compute spend, even if imported, gets monetised at home through productivity. A country that is a net buyer of AI inputs must, at minimum, be the most efficient internal consumer of them.

The bigger lesson

The KOSPI's nine-point-ninety-nine percent is not really a market story. It is a structural disclosure. Forty years ago a single oil price ran the world's inflation and growth narrative. We are not there yet with AI capex. But we are closer than is comfortable, and the trajectory is one-way. The job of policymakers in countries that neither make the chips nor own the models is to stop treating each AI-driven wobble as a curiosity and start treating it as a recurring macro shock with the same seriousness we reserve for crude.

Korea was the canary. The mine is the rest of us.

#AIcapex #KOSPI #EmergingMarkets #IndiaEconomy #GlobalMarkets #Semiconductors #MacroPolicy #ForeignFlows

Government Isn't A Hyperscaler

On Monday, Alphabet fell about 5%, dragging the communication services sector down with it. Memory chip stocks plunged in Asia overnight and the selling crossed the Pacific by Tuesday morning. Beneath the price action, the cause was specific and revealing: investors are starting to ask whether the enormous sums being poured into artificial intelligence will earn their keep, and reports of senior talent leaving Alphabet's AI teams added to the unease.

That question — will the AI capex pay off — is the right question for shareholders. It is the wrong question for a government.

What the market wobble actually says

The sell-off was narrow, not broad. The Russell 2000 closed above 3,000 for the first time even as the big tech names tumbled. That tells you the market is rotating, not collapsing. The doubt is concentrated in a handful of names whose valuations had assumed the AI trade would compound for several more years without a pause.

The question being asked is simple. Amazon, Microsoft, Alphabet and Meta have collectively guided to roughly 25 billion in capital expenditure for 2026. Their combined free cash flow is forecast to fall to about billion in the third quarter — a decade low. At that ratio, the cash being spent is no longer comfortably backed by the cash being earned. That is what the nervous side of the market is pricing.

Why this question doesn't translate to government

Public administration does not sell tokens. It does not have shareholders. Its “revenue” is taxes and its “product” is rights, services, and the slow accretion of public trust. The whole logic of equity-style ROI — free cash flow divided by capex — is structurally absent.

And yet, watch any AI tender written by any government this year and you will see private-sector language smuggled in. Pilots. Use cases. Productivity gains. Cost savings per FTE. We are evaluating public AI investments in the only vocabulary the consultants brought to the room, and the result is that everyone ends up arguing over a metric nobody in the citizen-service chain actually cares about.

From inside a national tax administration, having worked on conversational AI for citizens at scale, I can say something specific. The right number was never “queries handled per rupee of compute.” It was something closer to: did the next confused taxpayer get an accurate answer, in the language she actually speaks, in time to act on it, without having to travel to a counter? That is an outcome question. It is not a capex question.

An outcomes-first lens

If the market is pricing AI on cash flow, the government should price AI on three different things:

• Service latency. How much faster does a citizen get an answer, a refund, or a decision after the system is deployed?
• Service reach. How many more citizens, in how many more languages and pin codes, can the same service touch without adding counters?
• Officer leverage. How much higher-order work can the same officer do because the system has absorbed the routine?

None of these are radical. They are simply restatements of what the public sector exists to do. The discipline is to write them into the procurement document before the vendor walks in, not after the dashboard is built.

A proposal: separate the two stacks

Here is a concrete proposal. A government should split its AI estate into two stacks and evaluate them by two completely different rules.

The internal stack — drafting, summarisation, case retrieval, file review, internal search across decades of orders — can be evaluated commercially. Hours saved, error rates, contractor-substitution ratios. That is fair, because the work being replaced was already priced.

The citizen-facing stack — multilingual chatbots, eligibility navigation, guidance on a new statute, status tracking on a refund — must be evaluated as service delivery. The metric is not unit economics. The metric is whether a person previously locked out of a service is now inside it.

Confuse the two stacks and the second one will always lose to the first on a finance committee's spreadsheet. It will be quietly defunded the moment an AI valuation cycle turns. And, as Monday's tape made plain, the AI valuation cycle will turn.

The public sector organisations point

Professor Michael Ting's course on the Analysis of Public Sector Organizations at SIPA made an argument that has aged into something close to a law. Public agencies serve multiple principals — legislatures, ministers, courts, auditors, citizens — and the metrics they adopt silently decide which principal they end up serving. Adopt private-sector ROI metrics for public AI and the system will end up optimising for the auditor's spreadsheet, not the citizen at the window. That is not a hypothetical risk. It is the default trajectory.

What to do this quarter

Three moves, for any department about to sign an AI contract:

• Write the outcome metrics before the price negotiation, not after.
• Build at least one citizen-facing metric whose headline a non-technical minister can defend in question hour.
• Keep funding the citizen stack even when the headline AI trade in the markets is going through one of its periodic doubts. Especially then.

The market is reminding everyone this week that the private bet on AI is a bet. Government is not making the same bet. It is deploying a tool that should be judged by whether the queue moved. The discipline is to keep saying that out loud while the news cycle is busy saying everything else.

#AIinGovernment #PublicSectorAI #DigitalGovernance #AICapex #IndiaAI #Governance #PublicFinance

The Filing India Doesn't Owe

On 30 June 2026, exactly a week from now, multinational groups across more than three dozen jurisdictions will lodge their first GloBE Information Return. It is the most ambitious cross-border tax filing the world has ever attempted. India is not in the queue.

That is not a footnote. It is the single most important fact about Indian international tax this year, and almost nobody is talking about it.

The week the global minimum tax goes live

The OECD's Pillar Two is now operational. The rules apply to multinational groups with consolidated revenues of at least €750 million. If their effective tax rate in any jurisdiction falls below 15%, someone, somewhere, collects a top-up. Roughly 140 jurisdictions joined the inclusive framework back in 2021. Thirty-seven have actually legislated a Qualified Income Inclusion Rule or a Qualified Domestic Minimum Top-up Tax that bites from the 2024 reporting fiscal year.

The OECD was still soldering plumbing in the last weeks before the deadline. On 18 May 2026 it issued a common understanding allowing groups to file centrally in one jurisdiction and avoid duplicate local returns, provided each domestic office gets a notification. That a structural feature of the regime had to be settled eight weeks before the first deadline tells you something about how unfinished this compact still is.

Three countries that stayed away

The United States, China and India have not implemented Pillar Two. The American position is now formal: in January 2026 the US Treasury announced that US-headquartered groups would be exempt, and the OECD's 5 January Side-by-Side package legalised that exit by carving out a safe harbour for groups parented in jurisdictions with ‘eligible’ tax regimes. The US is, as of today, the only jurisdiction on the OECD Central Record with a confirmed Eligible SbS Regime.

India's stance has been quieter, and to my mind more considered. We participated in the framework. We never legislated the rules. We watched.

Why I think the wait was right

Pillar Two is not really a tax. It is a coordination mechanism that exports one country's view of what another country's tax base should be. It is the first time in modern fiscal history that a domestic legislature has been asked to outsource the residual taxing right on profits earned at home to a residence jurisdiction abroad. That deserves more scepticism than it gets in polite international tax conversation.

For India, the cost-benefit was always thin. The corporate rate here is 22%, or 25.17% with surcharge and cess. The concessional rate for new manufacturers is 15% statutory, around 17.16% effective. We are not a low-tax jurisdiction. Pillar Two only matters when you are below the floor; we mostly are not.

The price of joining would have been real. A QDMTT regime to design. A GloBE return architecture to build. A workforce to retrain in jurisdictional ETR computation. Disputes to defend under accounting standards that are not ours. And acceptance that the rules will be rewritten by an OECD working party in which our vote is one among many. None of that grows the base. It expensively confirms what we already collect.

What we still need to claim

The harder side is data. The 2024 GIR is the first time multinational groups will publish, in a standardised XML schema, a jurisdiction-by-jurisdiction picture of where their profits arose and what tax those profits paid. Other administrations will receive that file automatically. India, outside the exchange relationships, will not, unless we sign on to receive it. That is a transparency dividend we should be claiming whether or not we ever impose a single rupee of top-up tax.

Soft power is the other piece. The Side-by-Side carve-out is, in effect, a US-only privilege today. The OECD has signalled other jurisdictions may be added. ‘May’ is doing the heavy lifting in that sentence. If a future investor's post-tax compliance burden is lighter under a US parent than under an Indian one, we have not lost any revenue, but we have lost a piece of the architecture of who matters in the next decade of international tax rule-writing.

A proposal

The smart move is not to copy Pillar Two. It is to ask for the data, build the analytical capacity, and use the next eighteen months to find out where Indian profit shifting is genuinely costing us revenue. Three concrete steps.

• Sign the GIR Multilateral Competent Authority Agreement. The cost is administrative. The value is a structured view of every in-scope group's worldwide tax footprint, delivered automatically.
• Commission a quiet domestic study of jurisdictional ETRs for India-headquartered MNEs. Two or three years of clean data will tell us whether a future QDMTT would collect ten thousand crore or ten lakh. Right now the number is asserted, not measured.
• Use the Income-Tax Act 2025 transition window to bake in a minimum-tax-compatible computational backbone. If we later choose to switch on a QDMTT, the systems already speak the schema. Building it after a political decision is far more painful than building it now, while the law is still warm.

Pillar Two will either be remembered as the most consequential multilateral tax instrument since the League of Nations drafted the first model treaties in the 1920s, or as a noble experiment that fractured the moment its largest economy walked away. We do not need to guess which today. We need to stay liquid: positioned to step in, positioned to step out, owning the data either way. That is the case for sitting out 30 June with intent.

#PillarTwo #GlobalMinimumTax #IncomeTax #IndianEconomy #TaxPolicy #OECD #InternationalTax

When Ships Paid In Renminbi

Somewhere in the European Central Bank's annual report on the international role of the euro, published a few days back, there is a sentence that ought to have set off more alarms than it did. Settlement activity on China's Cross-Border Interbank Payment System rose by more than a third in the days around the outbreak of the Middle East war. Quieter still, the report notes that some ships made payments in renminbi via CIPS, or in crypto-assets, to transit through the Strait of Hormuz during March and April. A handful of transactions, in absolute terms. But a tell.

The dollar is not dying. It does not need to die for the world's payment plumbing to start looking less like a single pipe and more like a switchboard.

The Hormuz Tell

For seventy years, the working assumption of treasurers and central bankers has been that when a regional crisis flares, dollars buy you out of trouble. They buy fuel, they buy insurance, they buy the wire that gets a cargo moving. The ECB's detail tells us that assumption is starting to fray at the edges. When a ship in a hurry could not, for whatever reason, settle a passage in dollars, the alternative chosen was renminbi or, more telling, crypto.

The size of the shift in flow is worth dwelling on. Customer-related cross-border payments by Chinese banks in renminbi reportedly hit USD 1.4 trillion in March 2026, roughly 30% higher than the previous month. CIPS itself had grown a meagre 3% in 2025, after years of 20%-plus expansion; the war reversed that deceleration in a single month. None of this dethrones the dollar. All of it builds optionality for whoever pays attention.

A Defensive Pile Of Gold, And Not Much Else

India sits in this picture awkwardly. We have, by ECB's reckoning, added about 130 tonnes of gold to the reserves stack since 2022, alongside Turkey, China and Poland. That is a sensible defensive instinct after watching Russia's reserves get frozen. It is also where the imagination seems to have stopped.

The position is genuinely odd. Of the major economies thinking about reducing dollar dependence, we are the only one that already runs a domestic retail payments network most of the world envies, settles more real-time transactions than the rest of the planet combined, and has spent a decade quietly exporting that stack to friendlier jurisdictions. From inside a national administration that has built and operated citizen-facing digital infrastructure at scale, I can say with some confidence that the hard engineering problem of cross-border instant payments was solved at home long before it became geopolitically interesting. What is missing is the political will to treat the stack as strategic infrastructure rather than a soft-power side project.

Wrong Question, Right Answer

Most Indian commentary on the de-dollarisation theme falls into a trap: which bloc should we join, the dollar one or the renminbi one. This is the wrong question, and it is asked by people who confuse a payment rail with a treaty. India's interest is not in joining a bloc. It is in being able to settle, invoice, hold and route in whichever instrument is cheapest, safest and least politically charged on the day a particular contract has to close. The word for that is optionality, and it is built, not declared.

Three moves are worth making.

Treat payment corridors as foreign policy

UPI acceptance in the Gulf, Southeast Asia, parts of Africa and small island economies is being built piecemeal, often as tourism convenience. Stop calling it that. A corridor that lets an Indian importer pay a Vietnamese supplier in rupees or dong, without a dollar leg, is strategic plumbing. Build it with line items in the budget and missions actively negotiating acceptance, the way other countries negotiate visa-on-arrival regimes.

Insist on settlement clauses in trade agreements

The next ten free trade agreements India signs should, at minimum, contain a clause allowing settlement in either party's currency for a defined share of trade, with central bank windows providing convertibility at agreed bands. Project mBridge, the multi-CBDC platform connecting China, Hong Kong, Thailand, the UAE and Saudi Arabia, shows what a serious version of this looks like. India is conspicuously absent from that table; that is a choice we keep making by default.

Stop confusing gold with a strategy

A 130-tonne pile is a backstop. It is not active monetary architecture. The state can hedge tail risks in metal and at the same time build the live system that determines who pays whom in normal times. The two are not substitutes.

What The Classroom Did Get Right

Years ago at Columbia, in Prof. Richard Robb's International Capital Markets class, the formative lesson was that the international monetary system runs on inertia. It does not change because a paper is published or a summit is held. It changes when, in some operationally tedious moment a ship in a hurry, a bank under sanction, a captain refusing to wait the cheaper, safer instrument turns out not to be the dollar. That moment does not need to come at scale to matter. It needs to come reliably enough that the next CFO writes the alternative into her treasury policy as a permanent option, not an emergency one.

Xi Jinping's 1 February call for the renminbi to become a global reserve currency, taken alongside CIPS opening up to multicurrency settlement from the same date, is best read in that light. It is not a slogan. It is a procurement plan for whichever country wants to underwrite the next system.

The Habit, Not The Asset

The dollar's strength has never been an asset class. It is a habit, a default keystroke on every treasurer's terminal. Habits are sticky. They are also vulnerable to small, repeated, observable counter-examples. A few ships at Hormuz paying in renminbi, or in stablecoins routed through some Gulf trading hub, will not by themselves break that habit. But anyone reading central bank reports for a living should treat what happened in March and April as the rehearsal it was.

India holds the world's best retail payments stack and a serious geopolitical hand. Both are pointed away from each other today. The most useful thing the Government of India could do this year is to draw a line between them: to convert a fintech achievement into an instrument of statecraft. The next time ships are in a hurry at a chokepoint, the question worth being able to answer is whether any of them are settling in rupees.

#InternationalFinance #DollarDominance #UPI #Renminbi #CIPS #Geoeconomics #IndianEconomy #PaymentSystems

When GeM Learns Tamil

A handloom weaver in Karur. A carpenter in Bhubaneswar. A metal-fabricator in Rohtak. None of them has ever sold to a government department through GeM. Not because their work is poor; because the tender document is in English.

Last week, on 15 June, the Digital India BHASHINI Division and the Government e-Marketplace signed an MoU to integrate AI-powered language technologies into GeM, letting buyers and sellers transact across the platform in 22 Indian languages, with voice as a first-class input. The press release was polite and technocratic. Underneath it sits one of the more consequential pivots in Indian e-governance in years.

What was actually signed

GeM is the national procurement portal under the Ministry of Commerce. Government buyers, from ministries down to municipal corporations, use it to purchase goods and services from registered sellers. The transaction volumes are not small. Until last week, the platform spoke fluent English with Hindi as a polite afterthought. The new MoU plumbs the marketplace with BHASHINI's translation APIs, voice bots, domain-specific language models, and a voice-first interaction layer.

This is not a one-off. In recent weeks BHASHINI has signed similar agreements with DPIIT for the industrial ecosystem, with the Ayush Ministry for traditional health knowledge, with the Centre for Railway Information Systems, and with Kathmandu University to extend Indian-language AI into South Asia. The portfolio matters more than any single MoU. Together, they amount to a slow, deliberate plumbing of the Indian state with a shared language layer.

Language is infrastructure, not a feature

Many departments still treat language support as a checkbox. Get the portal translated to Hindi, drop in a few Tamil PDFs, declare victory in the next presentation. That mental model is wrong. Language is not paint applied at the end of a project. It is the medium in which citizens think, decide and act. A self-employed entrepreneur in Madurai will not navigate a fourteen-page English tender to bid on a six-lakh contract, even if a translation button exists somewhere.

What BHASHINI is building is something different: a horizontal language layer of the Indian state. The platform supports 36 Indian languages for text translation, 23 for voice recognition and speech synthesis, and reportedly processes more than 15 million AI inferences a day. Once that layer exists, any new government service, from a procurement portal to a hospital appointment system to a tax helpline, can become multilingual at the speed of an API call rather than at the speed of a fresh translation tender.

This is how digital public infrastructure should be built. UPI did it for payments. Aadhaar did it for identity. DigiLocker did it for documents. Language was the last big primitive that every department was hand-rolling badly for itself. It now has a shared standard.

The voice part, which most commentary will miss

The MoU foregrounds voice. Translation is the obvious win; voice is the deeper one. A welder in Latur with a smartphone and modest literacy will not type a procurement query into a form. He will speak it. Voice agents that understand Marathi, Telugu, Bengali and Bhojpuri properly are how the next two hundred million Indians will actually interact with the state.

From inside an administration that serves taxpayers at population scale, I can say this with some conviction: the bottleneck is rarely the legal text. It is the gap between the citizen's spoken question and the legal text's English answer. Closing that gap, in real time, across 22 languages, is harder than building any specific service. It is also more transformative.

Platform thinking, not product thinking

I have argued before, and still believe, that public-sector AI strategy which begins and ends with “let us build a chatbot” misses the point. A chatbot is a user interface. An interface alone solves nothing if the underlying service, data and language plumbing is broken. The BHASHINI-GeM partnership matters precisely because it inverts the usual order. It does not ship a flashy procurement assistant. It plumbs the marketplace with multilingual capability so that any future interface, whether chat, voice, IVR or mobile app, can speak the citizen's language without each department rebuilding the linguistics from scratch. That is platform thinking, and it is the right thinking for a state with thousands of services and finite budgets.

Three things that must follow

If this is to scale beyond a press release, three things should be insisted upon. One, every central ministry should publish a short, public roadmap for plugging at least one citizen-facing service into BHASHINI within six months; pick the highest-volume interaction and start there. Two, language quality cannot be self-certified by the platform that builds it; an external panel of native speakers, including from non-scheduled languages, should publish quarterly benchmarks the way RBI publishes inflation prints. Three, the income tax, GST and welfare-delivery systems, which together touch nearly every Indian, must move early. That is where the political payoff is largest, and where the harm of getting it wrong is also greatest.

Two final observations. The Eighth Schedule lists 22 languages, but India actually speaks well over a hundred; treating BHASHINI as the floor, not the ceiling, will matter. And this kind of infrastructure rarely makes news on the day it launches. It shows up two years later, when a self-employed seamstress in Tirupur wins her first government order in Tamil and does not remember a time it was otherwise.

#BHASHINI #GeM #DigitalIndia #AIGovernance #PublicProcurement #MultilingualAI #VoiceFirst #DPI

Tokyo Just Turned Off The Tap

The number is small. The symbolism is enormous.

On Tuesday, the Bank of Japan raised its benchmark rate to 1.0%, the first reading at that level since 1995. For most central banks a quarter-point move is routine. For Tokyo, it closes a chapter that has lasted longer than many working economists have been working.

The decision passed 7-1, with one dissenter citing growth risks. Governor Ueda missed the meeting after being hospitalised; Deputy Governor Himino, who chaired it, told parliament three days later that the bank remained committed to further hikes. That the move passed without drama is itself the story. Cheap yen is no longer the world's default setting.

What Tokyo actually tightened

The obvious analysis writes itself. The yen is weak, hovering near 160 to the dollar despite roughly 11.7 trillion yen of intervention in May. Wholesale inflation hit 6.3% that month, the highest since 2023, lifted by the Iran-driven oil shock. Real rates remain deeply negative even at 1%. None of that is wrong, but it misses the larger point.

For three decades Japan has effectively been the world's liquidity tap. Near-zero rates plus a deep, freely-traded currency made the yen the borrowing leg of the most successful carry trade in modern finance: borrow yen at almost nothing, swap into something higher-yielding from US Treasuries to Brazilian sovereign bonds to Indian rupee debt, pocket the spread. That trade has financed a startling share of cross-border risk for a very long time. When Tokyo moves the funding rate, every position built on it gets re-priced.

The signal beyond the number

What Tuesday closed is the optionality of staying loose. The Bank of Japan has spent a decade signalling that normalisation was conditional on wages, on inflation expectations, on the global cycle. The April hold was framed as a pause to absorb the Iran shock. The June hike says, in effect, that even with that shock unresolved, the bank judges the risk of inaction worse than the risk of action. Himino's testimony three days later, flagging the possibility that underlying inflation may deviate upward from the 2% target, was a polite way of saying more hikes are coming.

That changes the global plumbing in a way much domestic commentary will miss. A 1% policy rate today, plus a credible signal of 1.25% by year-end, is enough to make a slice of yen-funded positions uneconomic at the margin. Past BOJ hikes since 2024 have each been followed by sharp drawdowns in high-beta global assets within weeks. The mechanism is not mystery — it is forced deleveraging.

Through the India lens

The reflex in emerging markets, including ours, is to read these moves through the dollar lens. That is half the picture. The other half is who funds the dollar.

India has benefited handsomely from a long stretch in which a slice of foreign portfolio money in our bonds and equities was, somewhere up the chain, financed in cheap yen. As that funding gets more expensive, two things shift. The marginal cost of foreign capital into India rises even if the Federal Reserve does nothing further. And the patience of that capital shortens; a carry that looks attractive at a 25 basis point Japanese funding rate looks distinctly less so at 100, and brittle at 125.

There is an old lesson from any honest course on international capital markets that the funding leg of a trade often matters more than the asset leg. Tokyo just moved the funding leg. The corollary, for a finance ministry, is that long-duration, sticky foreign capital should be treated very differently in tax and regulatory design from money that is essentially a leveraged carry position. From inside a national tax administration, I have repeatedly seen the same instrument behave very differently depending on who is funding it. The funding mix is now changing.

What I would actually do

If I were sketching responses, three would be ordered ahead of the rest.

Rebuild the muscle for scenario work. Not a war-game, a quiet quarterly exercise inside the relevant departments — including the direct tax administration, which sees cross-border income in unusual granularity — on what a sustained 150 basis point repricing of yen-funded capital does to specific sectoral flows.

Read the data we already have. Indian tax filings, treaty disclosures and inbound investor reports carry a much richer real-time picture of cross-border behaviour than is generally appreciated. The question is whether anyone is reading them that way.

Stop treating every additional inflow as a win. Some inflows are savings looking for a long home. Some are leverage looking for a quick exit. Treating them identically was tolerable when Tokyo was paying the world to borrow. It is less so now.

None of this is forecasting doom. A Japanese policy rate at 1% is, in the long run, healthy normalisation — a return to a world where the price of money is set by something other than insurance against deflation. The point is simply that the era in which a non-trivial share of global risk-taking was quietly subsidised from a single building in Tokyo is closing. We should plan for the world that comes next, not the one we got used to.

#BankOfJapan #YenCarryTrade #MonetaryPolicy #EmergingMarkets #IndianEconomy #CapitalFlows #PublicFinance

Stop Building Chatbots.

Eighty-two percent. That is the share of inbound citizen queries an AI agent called Bobbi resolved in its first week across three English police forces, without a single hand-off to a human officer. The number matters less for policing than for what it telegraphs to the rest of government: the chatbot era, finally, is ending.

I say this with some scepticism about my own past. Anyone who has helped stand up a citizen-facing assistant inside a large national department knows the temptation to call any conversational widget a chatbot and declare modernisation complete. It is not. Bobbi, alongside Singapore's GovTech work and Estonia's interoperable agent network, signals that the next layer of public-sector AI will look very different from what most administrations are currently buying.

Chatbots answer. Agents act.

The technical distinction is sharper than the marketing suggests. A chatbot replies to a prompt. An agentic system is handed a goal — process this permit renewal — plans the steps, calls the databases, validates against the rules and executes the transaction. One produces text. The other completes a workflow.

This is why a recent World Economic Forum and Capgemini exercise mapping seventy core government functions sorts them more cleanly by workflow than by department. Eligibility assessment, document processing, fraud detection, permit issuance — these cut across ministries; they are the natural unit of analysis for an agent, not an org chart. Agents do not need to break silos. They operate outside them.

The chatbot habit is the trap.

The single most common mistake I see, both in India and abroad, is treating an agentic deployment as a chatbot upgrade. Same procurement template, same vendor, same knowledge base, a slightly cleverer model bolted on the back. That is not what the technology is for. The Capgemini survey of 350 public-sector organisations finds that ninety percent intend to explore or deploy agentic AI within two to three years, while Gartner forecasts that more than forty percent of those projects could be cancelled by 2027 — usually because the agency moved before understanding where the actual value sits.

The value sits in outcomes, not interactions. The right question is not can the bot answer this but what is the citizen actually trying to finish, and how many steps can we collapse into one supervised flow. An estimated one hundred and forty billion dollars in US federal benefits goes unclaimed each year because the application paths are too fragmented for the people who most need them. Most large administrations, India included, will find similar pockets if they look honestly: schemes whose stated reach far exceeds their actual delivery, not for want of policy but for want of plumbing.

What conversational AI for citizens actually teaches.

Citizen-facing conversational systems at national scale teach two unfashionable lessons. First, the volume of routine queries is far larger than any budget anticipated, and far more repetitive: a small set of questions accounts for most of the load. Second, when the citizen needs to complete something rather than learn something, the conversational layer hits a wall. The handover to forms, portals and back-office staff is where the experience breaks.

Agents are precisely the technology for that gap. In a direct-taxes context, an agent can read a notice, retrieve the relevant return, pre-fill a form against rule sets, cross-check historical filings and route only the genuinely ambiguous cases to a human officer. The administrator stays the architect. The agent does the clerical labour that nobody, on either side of the counter, particularly enjoys.

Bounded autonomy, glass-box defaults.

The discipline the field is converging on is bounded autonomy: being deliberate about what an agent is allowed to do, keeping a human meaningfully in the loop, and making every step auditable. The phrase that fits a public-sector context is glass-box governance. A chatbot answers, and the trail is shallow. An agent acts, and each action — every rule consulted, every database queried, every form submitted — should leave a perfect record. Used well, this is more accountable than the human-only system it replaces, not less.

The procurement template should change accordingly. Stop buying chatbots. Buy a workflow agent that ships with an audit log by default, with explicit, narrow permissions per task and a hard escalation rule for any case touching rights or material amounts. Bounded autonomy belongs in the contract, not in a vendor promise.

Where to start.

The most useful first move for any Indian department is unglamorous: pick one workflow that already exists end-to-end on paper or in disconnected portals — refund issuance, grievance redressal, a single notice-and-reply cycle — and rebuild it as an agentic flow with a human checkpoint at the decision. Measure completions, not interactions. Compare cost not to the chatbot it replaces but to the staff hours it returns. That number is what budget committees will eventually demand, and it is the only one that matters.

The chatbot was a useful detour. It taught millions of citizens that they could speak to the state in plain language and get a sensible answer. The agent is what turns that conversation into a completed transaction. The departments that grasp the difference now, and procure for it accordingly, will spend the next decade doing more with steadier headcount. The rest will spend it explaining why their bot still cannot actually do the thing.

#AgenticAI #PublicSectorAI #DigitalGovernance #GovTech #CitizenServices #AIinGovernance #IndiaAI

The Pause Is The Plan

At 10 a.m. this morning the Monetary Policy Committee kept the repo rate at 5.25%, unchanged for the third meeting in a row, with a neutral stance and a quietly composed press conference to follow. The headlines wrote themselves: RBI holds. Fixed-income desks shrugged. Equities opened a notch firmer. To anyone watching only the rate, today's decision looked like the absence of a decision.

It was not. The pause is the plan.

The rate is the top of a layered toolkit, not the toolkit

Think of Indian monetary policy as a stack. The policy rate sits at the top, visible, dramatic, easily understood. Below it lies a thicker, less photogenic layer: variable rate repo auctions, buy-sell forex swaps, open market operations, CRR adjustments, dollar liquidity windows for oil marketers, and the steady drumbeat of intervention in the spot and forward currency markets. Above 5.25% sits one lever. Beneath it sit a dozen.

The April hold was an early signal. Today's hold confirms the doctrine: until the data forces a move, the central bank will work the lower stack and leave the top untouched. DSP Mutual Fund's fixed-income team said it plainly in a pre-policy note, that the RBI rarely jumps straight to a rate move and follows a step-by-step sequence before pulling that trigger. Today's decision is a refusal to skip steps.

The shock is arriving through the exchange rate

Crude has been hovering near 96 dollars since the conflict in West Asia escalated. The rupee has slid to about 95 to the dollar, a level no one was forecasting a quarter ago. Wholesale inflation has crossed 8 percent. Retail inflation is still inside the band, but Icra's Aditi Nayar is right to flag that the second-round effects through fuel into transport, packaging and food are only beginning to show.

The temptation, particularly for analysts who default to a textbook reaction function, is for the RBI to hike in order to defend the currency. Standard Chartered already pencils in 50 basis points across FY27 and some expected the cycle to begin today. They were wrong, and I think rightly so. A defensive rate hike to prop up the rupee is the macroeconomic equivalent of treating a fever by raising the thermostat. It hurts the patient and does not fix the cause.

Gita Gopinath made the better point earlier this week: some rupee adjustment is what should happen when the world's oil price changes. Trying to keep the currency frozen would only postpone the move and bleed reserves in the process. The professional discipline is to let the price absorb part of the shock and use the lower-stack tools to keep the adjustment orderly.

Why doing nothing is the hardest trade in the room

To anyone who has watched government respond to external shocks from inside the administrative system, the instinct to act visibly and audibly in a crisis is almost overwhelming. Holding is the harder trade because it offers nothing for the news cycle to consume. There is no announcement, no ribbon to cut, no graph to point at.

What today protects is not the rupee, which will move as it must, but the credibility of the easing cycle behind it. Between February and December 2025 the RBI cut rates by a cumulative 125 basis points. Those cuts have transmitted into home loans, MSME credit and personal borrowing. A panicked reversal of that work, on the back of a single quarter of oil-led inflation, would shake the very domestic-consumption story that gives India its growth premium. The MPC's third consecutive pause is, in effect, a statement that the easing of last year will be defended.

This is the lesson at the heart of Prof. Richard Robb's International Capital Markets course at Columbia: a small open economy hit by a real external shock should let the exchange rate absorb the blow while the central bank manages the volatility, not the level. That is the doctrine on display this morning, even if the press release did not say so.

The harder question is what fiscal does next

The blind spot in today's commentary is that monetary policy cannot carry this alone, and should not have to. If crude stays near 96 dollars, the second-round inflation will come through fuel cesses, GST on logistics, and the price line of every state-distributed commodity. The fiscal authority owns more of those switches than the RBI does.

A serious response over the next two quarters has to include targeted excise rebates on transport fuels rather than blanket cuts, faster GST input-tax refunds to small businesses caught in the cash-flow pinch, quicker direct-benefit transfers to insulate the bottom three deciles from food inflation, and a clear medium-term fiscal anchor so the bond market prices the borrowing programme without demanding a higher term premium. Tax and expenditure administration, for once, can be the country's first line of macroeconomic defence rather than its slowest.

The closing thought

Markets are trained to read central bank announcements for what changed. The lesson of today is to read them for what stayed the same, and to notice what is doing the work underneath. The repo rate at 5.25 percent is the surface of the water. The currents that matter run below it: forex tools, liquidity operations, and a quietly disciplined refusal to let a temporary oil shock undo a year of carefully transmitted easing.

If the next 90 days bring a calmer crude tape, today will look like skill. If oil heads higher, the hold will be tested, but the architecture for the test is visibly in place. Either way, I think the MPC made the right call. Doing less, well, is harder than doing more, badly.

#RBI #MonetaryPolicy #IndianEconomy #RepoRate #MPC #Rupee #PublicFinance #CentralBanking

The Code Goes Live

Somewhere in a finance department of a company, a junior accountant is staring at a payment portal that now asks her to select Tax Year 2026-27 instead of Assessment Year 2027-28. That single drop-down is where the new Income-tax Act, 2025, actually begins. Not on 1 April, when it commenced. On 15 June, when the first advance-tax instalment falls due and a real bank account moves money under a real new statute.

Tax law, like a building, is finished only when somebody walks in.

The first deadline is the real commencement

The Income-tax Act, 2025, has been on the books for months. The Income-tax Rules, 2026, replaced the 1962 Rules from 1 April. Hundreds of FAQs have circulated. None of that is the test. The test is the 15 June advance-tax instalment for Tax Year 2026-27, the first time a taxpayer estimates a year's liability under the new code and pays fifteen percent of it.

That is when the law moves from print to pay-in. Until then, every conversation about the new Act has been a rehearsal. From 15 June, the choreography is live.

Two statutes, one tax year

There is a peculiar transition reality that gets understated. The 1961 Act stands repealed from 1 April 2026, but the repeal does not disturb anything relating to tax years before that date. Assessments, appeals and proceedings for earlier years continue under the old Act. The advance-tax instalment due in March 2026 for FY 2025-26 was governed by the old law. The instalment due on 15 June 2026 is governed by the new one.

So the department, and every CFO of any scale, is now running two statutes simultaneously: one for past income, one for current income. From inside any large tax administration, this is the un-televised reality. A transition is not a date; it is a multi-year overlap, where the same officer handles a 2023-24 reassessment under the old code in the morning and a 2026-27 advance-tax compliance under the new code after lunch. The simplification on paper does not eliminate that doubling of cognitive load. Only time does.

The small print of a clean statute

The new Act is shorter, cleaner and more readable than the 1961 Act after six decades of grafts and provisos. But cleanness creates its own friction at the implementation layer. "Previous year" has become "tax year". Section numbers have shifted: advance tax now sits in Sections 403 to 410 rather than the familiar Section 208 onwards. Form 16 is now Form 130. Form 3CEK is now Form 173. Form 26AS is now Form 168.

None of this changes any substance. All of it changes muscle memory. Every payroll system, every ERP, every accountants-office macro, every internal departmental tutorial, every taxpayer's mental shorthand must be rewritten. The headline simplification will be felt only after that rewriting is done. The cost of clarity is paid up front, in transition friction; the dividend comes back later, in compliance ease. Reformers tend to celebrate the first. Only practitioners feel the second.

An administration learning in public

I think the more interesting question is what a new code does to the administration that runs it. A tax department is, in operational terms, a very large rule-execution machine. When the rulebook changes, every loop in that machine must be re-instructed. The portal must accept new minor-head codes. Notices must cite new sections. Officers must learn to draft orders in the new language without slipping back into the 1961 cadence they have known their whole careers. Helpline scripts must be rewritten. Internal training becomes, in effect, an ongoing exam.

This is where productivity either materialises or evaporates. If the first advance-tax cycle runs smoothly, if challans clear, refunds reconcile, mismatches are caught early, then taxpayer confidence in the new regime is established for the next decade. If it is messy, every news cycle of the next few months will be about glitches, and a reform that is substantively sound will be remembered as operationally rocky. The legislative work is over. The implementation game has just begun.

A small proposal for the transition window

One concrete suggestion. Through the first full tax year under the new Act, every taxpayer-facing communication, intimation, notice, demand, refund order, should carry the equivalent old-Act section in parentheses next to the new one. A demand under Section 405 of the 2025 Act should read "(corresponding to Section 234C of the 1961 Act)". This is not a dilution. It is a translation layer.

It would cost the department almost nothing. It would save tens of thousands of taxpayers from a private translation exercise each. It would also reduce the small but real risk of misdescription in appellate orders during cross-over years, where a citation gets stuck between two statutes. Translation layers age well. They quietly disappear once they are no longer needed, leaving a cleaner system behind. The concordance table mapping the old sections with the new one needs to get etched in the muscle memory.

For most taxpayers, 15 June 2026 will feel like any other deadline. For the new Income-tax Act, 2025, it is the day the simulation ends and the actual run begins. Everything written about the new code so far has been on a whiteboard. From that date, it is on the ledger.

#IncomeTaxAct2025 #AdvanceTax #TaxYear2026 #IndianTaxation #TaxAdministration #CBDT #PublicFinance

Who Vets The Frontier Model?

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