Ganga — Attestation Pilot

Ganges.ai · sovereign edge AI inference with hardware-signed DPDP compliance certificates

PILOT v1.2 · sample snapshot 2026-09-16T23:33:42Z · synthetic pilot data

Pilot posture one screen, every customer, site and node

2001

customers on pilot

2994

edge sites

PSU offices, factories, hospitals, petrol pumps

2001

attested nodes online

0 offline (jobs queue + drain)

6960

jobs run

6479 certified · 481 consent-blocked

6479

compliance certificates

3653 active

2585

revoked

ad hoc + consent-withdrawal cascades

241

expired

artefact validity windows

1440

consent artefacts

1130 active · 310 withdrawn

413

CERT-In incident reports

6-hour SLA artefact

808

grievances resolved

0 open · 0 SLA-breached

876

DR restore drills passed

876 snapshots · 876 verified replicas · last RPO 0.02s / RTO 0.0s

19195

audit ledger entries

hash-chained, checkpoint-verified

key rotations

per-node rotation with full history

How a job becomes compliance evidence

1 · Onboard

Customer joins a pilot tier (10 / 20 / 25) with sites and attested edge nodes.

2 · Consent gate

Every job is checked against a registered DPDP consent artefact - purpose, data class, scope, validity window. No consent, no compute.

3 · On-prem inference

The job runs on the site's own hardware. Personal data never leaves the building; it is destroyed with proof.

4 · Signed certificate

The node and the Agni-Shield co-sign a tamper-evident DPDP compliance certificate: consent verified, data destroyed, residency attested.

5 · Verify anything

Any auditor verifies any certificate against the hash-chained ledger - valid, revoked or expired, with the reason.

Certificate verification recorded API responses from the sample pilot

A healthy certificate: VALID

{
  "verdict": "VALID",
  "certificate_id": "04f2d5fd-98f8-48a5-a35a-c1083bf5f644",
  "chain_head_seq": 19195,
  "latency_ms": 27.5
}

After a consent withdrawal cascade: REVOKED

{
  "verdict": "REVOKED",
  "certificate_id": "9b905cbf-b1e6-48fd-a31a-b424604fc18b",
  "reason": "post-hoc incident drill",
  "latency_ms": 0.7
}

DPDP compliance, built in

Consent as an object. Registered artefacts with purpose, data class, scope and validity windows - expired or mismatched consent blocks the job, with the reason on the audit trail.
Withdrawal cascades. A customer withdrawing consent revokes every live certificate it issued, automatically and traceably.
Grievance redressal. A data principal can file against any certificate; resolution is tracked against a published 72-hour SLA, breaches flagged.
CERT-In reporting. Security incidents produce a report artefact inside the 6-hour window, linked to the affected certificates.
Disaster recovery. Point-in-time integrity-hashed snapshots replicate to a second attested node - a replica that cannot reproduce the state hash is rejected. Restore drills re-verify certificates from the replica and measure RPO and RTO; a drill that cannot re-verify every certificate FAILs. Every step is hash-chained to the ledger.
Hardware attestation. Every node holds an Ed25519 keypair (simulated TPM); certificates carry node + shield signatures; keys rotate with full history.
Offline resilience. A node going offline queues its jobs; the queue drains when it returns - no lost work, no silent gaps.

What an auditor pulls customer audit pack (excerpt)

{
  "customer": {
    "id": "b5f191c7-e74e-4c79-81a1-650a477c16bf",
    "name": "msme_factory_owner-17-1609",
    "sector": "MSME",
    "tier": 25,
    "dpo": {
      "name": "",
      "email": "dpo1609@example.in"
    }
  },
  "jobs": {
    "certified": 8
  },
  "certificates_issued": 8,
  "certificates_revoked": 1,
  "attestation_pass_rate": 1.0,
  "consent_blocks": 0,
  "grievance_sla_breaches": 0,
  "certin_reports": "0 reports on file"
}

Grievance redressal, on the record latest resolved grievance

{
  "status": "RESOLVED",
  "grievance_id": "grv-d8c0b25591b4",
  "customer_id": "3d3ed7de-8d31-44bb-adeb-a9946a725e95",
  "cert_id": "9b905cbf-b1e6-48fd-a31a-b424604fc18b",
  "description": "purpose beyond consent",
  "sla_hours": 72.0,
  "filed_at": "2026-09-16T19:49:59Z",
  "sla_due_at": "2026-09-19T19:49:59Z",
  "resolved_at": "2026-09-16T19:49:59Z",
  "resolution": "job data re-verified as destroyed; explanation sent to principal",
  "sla_breached": false
}