The challenge
Constituent grievances arrived through letter, email, IVR, and walk-in channels across 11 official languages, with no unified routing layer. Tabling questions, briefing notes, and audit lookups depended on manual collation across siloed secretariat systems, and any third-party SaaS was a non-starter on data-residency grounds.
How we approached it
Ajuni shipped a fully on-prem deployment on the Parliament's sovereign cloud, with Sevak handling citizen-side intake across 11 languages and Veer signing every routing decision into an immutable audit ledger. Integration was scoped to the existing PRIDE secretariat workflow and the central grievance portal, with zero outbound network egress.
Outcomes in production
- 11-language citizen intake routed end-to-end on-prem
- Audit ledger signed every routing and reply
- Secretariat lookup time dropped from hours to seconds
- Zero third-party data egress across the deployment
- Sovereign cloud posture cleared by internal security
Stack & guardrails
Integration & deployment
- On-prem sovereign cloud · NIC
- Llama 3.1 70B self-hosted
- IndicTrans2 for translation
- PRIDE secretariat integration
- Postgres + immutable audit ledger
- Bharat Voice IVR bridge
Compliance & audit
- Sovereign data residency
- DPDP Act 2023
- CERT-In audit
- Parliamentary records compliance
Timeline
-
Week 0–2
Sovereign-posture scoping
Use cases ranked with secretariat; on-prem topology approved by NIC.
-
Week 3–5
Language pack onboarding
11 Indian languages tuned on archived constituent correspondence.
-
Week 6–9
Shadow ledger run
Sevak observed live intake; Veer signed every outcome for review.
-
Week 10–12
Production cutover
Full constituent intake routed through agents with daily ledger audit.
