r2-gov-v1 — Profile for Indian government deployments
A sectoral profile extending the base R+2 standard for Indian central government, state government, and public-sector undertaking AI deployments. Aligns receipt fields with RTI Act §4, DPDP Act §8, and IndiaAI Mission compliance obligations.
1. Purpose
The base R+2 standard at dcslabs.ai/standard is sector-agnostic. This profile constrains R+2 for Indian government use cases by:
- Adding required extension fields for DPDP §8 data principal identification and consent tracking.
- Adding required fields for RTI §4(1)(b)(xvi) proactive disclosure.
- Mandating an additional
action_typenamespace (gov.in/*) for India-specific operations. - Specifying language requirements (English + at least one Indian language for citizen-facing actions).
- Aligning audit-export format with the IndiaAI Mission draft procurement guidance.
2. Extension fields
An R+2 receipt conforming to this profile MUST include the following fields under extensions:
| Extension key | Type | Description |
|---|---|---|
| gov.in.dpdp_consent_ref | string | UUID linking to the consent artifact under which the action was performed. Required for any action processing personal data of an Indian resident. |
| gov.in.purpose_code | string | Purpose code from the IndiaAI Mission purpose registry (e.g., SKILL-INDIA.001, HEALTH-NHM.003). Required for all actions. |
| gov.in.data_principal_id | string | Tokenized identifier for the data principal. MUST NOT be a raw Aadhaar number or other reversible identifier. Required when personal data is involved. |
| gov.in.rti_disclosable | boolean | True if this action's record is subject to proactive RTI disclosure under §4(1)(b)(xvi). Default: true for central government, varies by state. |
| gov.in.air_gap_required | boolean | True if the action must be performed in an air-gapped environment (DRDO, ISRO, sensitive ministries). When true, receipt MUST NOT include any IPFS pinning references. |
| gov.in.language_codes | array of strings | ISO 639-1 codes for languages this action's output was made available in. MUST include "en" and at least one Indian language for citizen-facing actions per the IndiaAI Mission multilingual guidance. |
| gov.in.minor_data | boolean | True if this action processes data of a minor (per DPDP §8(8)). When true, additional safeguards from §8(8) apply. |
3. action_type namespace
Actions performed under Indian government deployments SHOULD use the gov.in/* namespace for the action_type field. Standard sub-namespaces:
gov.in/citizen-service/*— actions taken on behalf of a citizen (e.g., document issuance, status lookup)gov.in/decision/*— administrative decisions made or assisted by an AI agentgov.in/disclosure/*— RTI disclosure actionsgov.in/audit/*— internal audit and compliance actionsgov.in/inter-ministry/*— cross-ministry data sharing actions
4. Compliance mapping
This profile maps R+2 receipts to specific Indian law and policy obligations:
| Obligation | R+2 field satisfying it | Notes |
|---|---|---|
| DPDP §8(4) Accuracy | Memory write/update receipt with chain integrity | Chain pointers detect any tampering of past records. |
| DPDP §8(5) Safeguards | signature + canonical JSON | Cryptographic safeguards demonstrate technical and organizational measures. |
| DPDP §8(6) Breach notification | action_type: gov.in/breach-disclosure/* | Signed receipt of the 72-hour notification. |
| DPDP §8(8) Children's data | extension: gov.in.minor_data | Flag triggers additional verification requirements upstream. |
| RTI §4(1)(b)(xvi) | extension: gov.in.rti_disclosable | RTI-applicable actions are flagged for proactive disclosure. |
| IndiaAI Mission procurement guidance | Full receipt chain + R+3 export format | Demonstrates auditable AI per draft procurement requirements. |
5. Air-gapped operation
When extensions.gov.in.air_gap_required = true, conforming implementations MUST:
- Not pin receipts to IPFS or any external storage.
- Not include
prev_receipt_cidreferencing externally-pinned content. - Store all receipts within the ministry's controlled infrastructure.
- Generate audit exports on demand without network access.
DCS Labs offers a Sovereign-tier deployment that supports air-gapped operation by default. Contact [email protected] for sovereign deployment guidance.
6. Worked example — citizen service action
A receipt for an AI agent issuing a digital certificate to a citizen under the Skill India scheme:
{ "spec_version": "r2/v0.1", "agent_pubkey": "u4yK_lH8Z6vJ...", "agent_id": "skillindia-cert-001", "action_id": "3f8a7c12-8b91-4e2c-9b3a-5f7d8e1a2c4b", "action_type": "gov.in/citizen-service/cert-issuance", "action_data": { "cert_id": "SI-2026-04829361", "course_code": "DSC-Web-Dev-101", "issuing_state": "MH" }, "occurred_at": "2026-05-21T15:42:08.123Z", "prev_receipt_cid": "sha256:bafy2bzaceabc...", "nonce": "k3J9p2qR7sT5vXyA", "extensions": { "gov.in.dpdp_consent_ref": "consent_a83f_2026-04-15", "gov.in.purpose_code": "SKILL-INDIA.CERT.001", "gov.in.data_principal_id": "dp_token_8f3a91cd", "gov.in.rti_disclosable": true, "gov.in.air_gap_required": false, "gov.in.language_codes": ["en", "hi", "mr"], "gov.in.minor_data": false }, "signature": "sig_base64url_86chars..." }
r2-verify and confirm: (a) Skill India's agent actually issued this certificate, (b) consent was on file at consent_a83f_2026-04-15, (c) the action is RTI-disclosable, (d) the citizen received the credential in their language. No trust in DCS or the ministry required.
7. Adoption checklist
For a ministry or PSU adopting this profile:
- Generate Ed25519 keypairs for each AI agent system.
- Register agents in the IndiaAI Mission agent registry (when launched).
- Maintain the purpose code registry under
gov.in.purpose_code. - Implement the receipt-issuing layer (use
@trdnetwork/mcp-serveras reference). - Stand up a public verification endpoint (read-only, no auth required, per RTI).
- Annual audit using
@trdnetwork/r2-verifybundle mode (see Tutorial 06).
8. Governance
This profile is a public draft submitted to MeitY's standards desk and the IndiaAI Mission technical committee. Once a government body (MeitY, NIC, state IT department, or IndiaAI Mission) formally adopts the profile, the editorial group expands to include their representatives. Until then, DCS AI Technologies maintains the draft.
The profile is and will remain MIT-licenced. No royalty, no licensing fee, no procurement contract required.
Contact
Editorial: [email protected]
Government affairs: same address, prefix subject with "[Gov]"
Source repository: github.com/DCS-LabsAI/r2-standard