Sovereignty Theatre: How to Spot It

The evaluation room had a projector and a flag in the corner. The vendor’s first slide was the flag, the Ashoka lion, and the words Sovereign AI for Viksit Bharat. The second slide was an India-region map pin. The third was a DPIIT certificate. The technical member asked where a prompt went if the local card was busy. The presenter went back to the flag.

That room is not rare. Procurement teams are being asked to score a feeling. Theatre is any claim that substitutes a symbol, a certificate or a geography pin for a packet path. This checklist is how you stop scoring the feeling.

It is written for procurement officers and committee secretaries who have to mark bids this quarter. It is rude on purpose. Vendors who do the work will not mind. Vendors who brought only the flag will.

The theatre checklist

Mark each row as evidence shown, promised in writing, or absent. Absent is a no.

Print this table. Take it into the demo. Write on it.

Claim you will hear	Why it is theatre if unsupported	Evidence that would make it real
Sovereign / Bharat LLM / India-first	A name is not a path	Diagram of inference, logs, tools; fail-closed demo
India region	Disk geography is residency, not control	Admin-plane location; key custody; subprocessor list
DPIIT recognised	Eligibility, not architecture	Still need the DPA schedule and the egress test
Data never used for training	Often means not in the next foundation model, maybe	Ban that names prompts, eval sets, embeddings, RLHF
On-prem available	Often a thin client plus a collector	Install on a VLAN with no default route; survive
Air-gap ready	Often means we can email you a build once	Signed artefact, offline licence, update runbook, no DNS
DPDP compliant	A date and a statute are being used as a sticker	Role map, basis table, deletion drill, transfer decision
Certified / audited	Wrong scope, old date, or a marketing ISO	Report that covers this product and this collector
Made in India	May be true of the entity or the invoice	Still ask where the model host lives
Used by X ministry	A logo is not a referenceable architecture	A named public statement or a call you are allowed to make

Four questions that end the show

1. Pull the WAN. What still works, and what dies?
2. Show the last outbound hostname from a production-like install.
3. Delete a fictional principal from every store, including the vector index, in front of us.
4. Name every legal entity that can read a prompt, including affiliates and support.

A serious vendor may need a day to prepare those four. A theatre vendor will need a new slide. Give the day. Do not give the contract instead.

How theatre sneaks into the commercial bid

Theatre is not only a slide. It is a commercial format that scores adjectives. If your comparison table has a column called sovereignty with a drop-down of yes or no, you have invited the flag. Split the column into the four questions, each with an evidence cell. A bid that leaves an evidence cell blank is a no, even if the cover letter is lyrical.

Watch the reference-site trick. A ministry logo from a hackathon, a workshop, or a group-company product is not a production citation. Ask for the workflow name, the data class, and whether the WAN-pull was done. If the bidder cannot say those three things about their own reference, strike the logo.

Watch the certificate pile. ISO, SOC, DPIIT, a startup India badge, an empanelment. Each certificate answers a question. None of them answers where the prompt goes when the GPU queue is full. Put certificates in an eligibility envelope. Do not let them leak into the technical score for sovereignty.

Objections

We are insulting serious Indian companies. We are insulting adjectives. Serious Indian companies will show the packet path and should be marked up for it.

Demos cannot pull the WAN. Then the demo is a film. Schedule an install.

Other committees accepted this paper. Other committees are not signing your file.

Words that should never score points

Sovereign, Bharat, Atmanirbhar, DPDP-ready, bank-grade, military-grade, air-gap-capable, India-first, trusted. None of these is a control. If a bid uses three of them in a paragraph that does not name a hostname, mark the paragraph as colour and move on.

Capable and ready are especially cheap. Capable means a SKU exists in a brochure. Ready means a salesperson has a slide. Ask for the last install that survived a WAN-pull. If there is no last install, the capability is a wish.

Used by the government is not a word, but it behaves like one. Government is not a single fiduciary. A municipal FAQ and a scholarship case file are different purchases. Demand the workflow, or treat the claim as colour.

A 30-day anti-theatre habit

• Week 1: adopt the table as a standing annex to every AI evaluation.
• Week 2: train the committee secretary to ask the four questions.
• Week 3: run the questions on one incumbent tool you already paid for. Expect discomfort.
• Week 4: write the discomfort into the next RFP as mandatory evidence, not as oral wit.

What goes in the file

The marked table, the notes from the WAN-pull, the subprocessor names spoken aloud, and any logo claim you decided to ignore. Future you will need proof that the flag was not the control.

Hold Prcept AI to this checklist. An Indian LLP and a DPIIT recognition should not get us a free cell.

How to defend this in the file

A P2 Procurement will be asked to explain “Sovereignty Theatre: How to Spot It” to a secretary who has ten minutes. Do not start with the model. Start with the store, the hop, the clause, or the residual risk. “fake sovereign AI claims” is a search phrase. The file needs a decision.

Theatre is a slide that uses the flag as a control. Spot it with questions that have packet-shaped answers, then score the answers, not the adjectives. DPDP does not define sovereign AI. Transfers can be lawful and still be a bad idea. Sector circulars can be stricter than DPDP. Write which instrument you are using.

If you cannot name the Data Fiduciary, the processor, the location of traces, and the erasure method, you are not ready for production personal data — whatever the architecture PDF says.

• One sentence on lawful basis or the procurement rule you are invoking.
• One sentence on where prompts, embeddings and logs live.
• One sentence on who can compel the operator.
• One artefact: packet capture, DPA schedule, or deletion certificate template.

Close this loop before the next CAB

Put “Sovereignty Theatre: How to Spot It” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P2 Procurement, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “fake sovereign AI claims” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

A ten-minute spotting drill

Open the vendor PDF. Highlight every use of sovereign, India region, and no data leaves. For each highlight, demand one artefact: a facility name, a key holder, an egress list, or a DPA schedule. If the artefact is a logo, it is theatre.

Then open staging. Disable outbound internet. Run the demo they showed the committee. Theatre dies when the demo dies. Real stacks keep drafting a noting.

1. Count the adjectives on slide one. More than two is a smell.
2. Ask where last week's traces live. 'Our portal' is theatre.
3. Ask who can freeze the tenant. If they do not know, they are not sovereign operators.

What the next noting must contain

“Sovereignty Theatre: How to Spot It” belongs in a file, not only in a search result. A P2 Procurement should be able to point at one artefact that proves “fake sovereign AI claims”: a packet capture, a processing schedule, a scored evaluation row, a dated notice, or a refusal rule. If the only evidence is a slide, you have a heading.

Theatre is a slide that uses the flag as a control. Spot it with questions that have packet-shaped answers, then score the answers, not the adjectives. DPDP 2023 does not define sovereign AI and does not write a blanket localisation rule for every model hop. CERT-In’s 28 April 2022 directions still set specified incident clocks and 180-day log retention in India for in-scope events. The November 2025 AI governance text is guidance, not a statute. A Proprietary Article Certificate, when it is lawful, lives in GFR Rule 166 — not Rule 161.

Write three dated sentences under C1 Sovereignty & Data Residency: what was decided, which designation owns it after the next posting order, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the designation that owns “fake sovereign AI claims”, plus a deputy.
• Attach one artefact a stranger can open next year.
• Name the instrument you are actually using — Act, direction, GFR clause, GeM term, or guideline paragraph.
• Leave unsourced percentages, GMV slides and house forecasts out of the noting.
• Revisit when the model, the SI, the notice, the region or the posting changes.