Agent Governance Charter for Departments

A secretary asked for 'the AI policy' the week a newspaper called. What existed was a 70-page consultant PPT, an unsigned DPA, and a WhatsApp group named Agent Pilot. Nobody could show a page that said what the department had decided. The newspaper was not wrong to smell a vacuum.

This is a charter template a department can actually sign. Two to four pages. It is not the RFP, not the DPA, not the ISMS, not the Guidelines PDF. It is the spine those documents hang from: purpose, roles, gates, trail, data rules, how you use the 2025 sutras, and who sits where when the agent is wrong. Unsigned, it is this article. Signed, it is the first exhibit in a CAG query and the first attachment to a tender.

Not a statutory form. Not legal advice. Counsel must fit it to your allocation of business, your delegations, and any state instrument that already claims the ground.

The page map

Page 1: why we are using agents, which workflows are in, which are out, and the sentence that no production personal data moves without a DPA. Page 2: roles — fiduciary owner, CIO, DPO, CISO, competent authorities, vendor as processor. Page 3: gates, trail, isolation stance, language honesty. Page 4: error seats, citizen correction, review date. If you need page 5, you are writing a manual. Put manuals elsewhere.

Paste-ready headings. Each heading needs three to six lines, not an annexure.

Heading	Three lines that must appear	Points at
Purpose and scope	Named workflows; explicit outs (no autonomous sanction, no 22-language claim)	RFP chapter 1
Roles	Fiduciary person, DPO, CISO, process owner; vendor is processor	DPA
Data rules	Location, training ban, subprocessors, 180-day Indian logs, erasure including embeddings	Data-handling schedule
Gates	Drafts may be free; speech and commitments stop for named roles	Workflow config
Trail	Seven fields in a department store	Annex S / SIEM
Guidelines	Sutras operationalised as artefacts; not a DPDP substitute	One-pager in the file
Errors	Four seats; citizen correction path; no 'the model did it'	Incident SOP + MSA
Review	Date, officer, what will be re-eval'd	Calendar

Who signs

The secretary or the head of the department signs the charter. The CIO, DPO and CISO countersign the annex that names them. A vendor does not sign the charter. They sign the MSA that obeys it. A consultant does not sign it either. If the only signature is a vendor's, you do not have a charter. You have a brochure.

Political leadership can bless the purpose paragraph. They should not be asked to bless a model family.

How it connects to the buy

The RFP says 'bidders shall satisfy the department Agent Governance Charter vX, attached'. The evaluation sheet has a row: any conflict with the charter is a fail. The DPA repeats the data rules. The incident SOP repeats the seats. When those four documents disagree, the charter wins and the others are corrected — unless a statute says otherwise, in which case the statute wins and the charter is corrected. Write that supremacy sentence.

• Supremacy: statute > charter > MSA/RFP. Never the vendor FAQ.
• Version number on every fork.
• A review not more than twelve months out.
• A ban on unsanctioned unofficial chat tools for official records, said plainly.

What to leave out

Model brands. Benchmark scores. A 20-page ethics essay. A copy-paste of the entire Guidelines PDF. Manpower charts. Anything you cannot inspect in a drill. The charter is a decision record, not a library.

Leave out a promise that the department is 'Guidelines compliant'. Map the sutras to the artefacts already in this charter — gates, trail, seats, training ban — and stop. Leave out a sentence that DPDP is satisfied because a human clicks. Those two sentences are how charters become vendor brochures with a government crest.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

Four pages cannot be a policy.

Four signed pages plus pointed annexures is a policy. Seventy unsigned pages is a slide share. Secretaries sign the first. They do not sign the second.

We will wait for a ministry-wide model charter.

If one arrives, you will fork it. Meanwhile you are running or about to run an agent. An unsigned wait is a vacuum. Write v0.9 and date the review.

Legal will expand it to forty pages.

Let legal write a companion opinion. Keep the signed spine short. If they insist on merging, number the decision sentences so they cannot be lost in the opinion.

A charter will slow the tender.

A charter is what stops the tender from being rewritten three times in pre-bid. It is a schedule compressor if you write it first.

A sample page one you can argue with

Purpose. This department will use agents only to draft first notings and retrieve circulars on named workflows listed in Schedule W. Agents will not issue sanctions, reject benefits, or send citizen-facing text without a named competent officer. We do not claim Eighth Schedule coverage. We do not claim DPDP is satisfied by a human click. We do not claim the 5 November 2025 Guidelines are a statute.

Data. No production personal data moves without a signed DPA. Training on our prompts, traces, embeddings and outputs is banned. Logs required for CERT-In practice land in our Indian store for at least 180 days. Embeddings are in scope for location, the ban, and erasure, subject to audit holds counsel names.

That is already half a charter. Add the role names, the gate table, the seven-field trail, the four error seats, and a review date. Sign it. Attach it to the next paper that tries to buy a miracle. The newspaper, the CAG party, and the pre-bid room can all read the same four pages. That is the test of a charter: three hostile readers, one text.

A fourteen-day charter you can put on a table

Do not start from a blank ethical treatise. Start from the table in this article and last month's real workflow.

1. Days 1–3: CIO drafts the four pages from the table, using one real workflow as the example.
2. Days 4–7: DPO, CISO, process owner, counsel red-pen. Delete adjectives.
3. Days 8–10: competent authority checks the gate sentences against live delegations.
4. Days 11–12: secretary's office. One sitting.
5. Days 13–14: attach v1 to the RFP or to the running pilot. Book the review date.

How this shows up in the file

The signed PDF, the version number, the review date, and a one-line supremacy sentence. That packet is the charter. Everything else is a child document.

If you cannot get a signature, you do not yet have governance. You have a reading group. Say so, or get the signature.

This article is informational field guidance for Indian public institutions, not legal, procurement, security-accreditation or engineering advice. Confirm against the current Gazette, GFR, GeM term, CVC instruction, CERT-In direction, DPDP text, departmental manual and your counsel before you file it.

How this survives CAG, RTI or the Board

“Agent Governance Charter for Departments” is not a workshop slide. A P1 CIO/CTO will have to reconstruct a decision after the officer who clicked approve has been transferred. Write the artefact that lets a stranger replay the case: the log fields, the approval, the override, the register row.

A charter is the short signed document that the RFP, the DPA and the incident SOP all point to. If it is longer than four pages, it will not be read. If it is unsigned, it is a blog. India AI Governance Guidelines (November 2025) are guidelines, not a statute. DPDP still allocates fiduciary duty. Delegation of Financial Powers still allocates who may spend. Do not hide those instruments behind the word governance.

If you cannot show who acted, on which purpose, with which data class, and who could have refused, you do not have accountability. You have a chatbot with a charter PDF.

• Name the owner of “AI governance policy template” inside the department, not the vendor.
• Keep CERT-In-relevant logs in India for the required period.
• Store overrides with a reason an auditor can read.
• Put the workflow on the AI register before it touches a citizen.

Close this loop before the next CAB

Put “Agent Governance Charter for Departments” 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 P1 CIO/CTO, not “the vendor.”

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