AI-Kavach-Pack
Describe an AI system once. Get its governance pack in one command.
You fill in one short form about an AI system: who uses it, what it does, what data it touches, which model runs it and which controls exist. AI-Kavach-Pack gives you back the documents a risk committee, a DPO and a board ask for, plus a gap check that can block a release in CI.
Kavach (कवच) means "armour" in Hindi.
Why
Most teams in India do AI governance in spreadsheets and slide decks, rewritten for every system and out of date by the next release. The paid platforms are built for large enterprises and mostly for EU and US rules. Open-source tools exist for single documents, such as model cards, but not for the whole pack an Indian review needs: risk tier, DPDP duties, vendor questions on data location and training, and agent limits.
AI-Kavach-Pack turns the AI Governance Playbook into a working tool, so the review starts from facts about the system instead of a blank template.
30-second demo
pip install ai-kavach-pack
kavach-pack demo
This builds packs for three fictional systems:
| Example system | Tier | Blockers | Why it is in that tier |
|---|---|---|---|
| Meeting Summary Drafts | Low | 0 | Internal team, drafts only, no personal data |
| Loan Document Reader | High | 4 | Financial and ID data in a credit decision |
| Bank Support Assistant | High | 10 | Customer-facing agent that blocks cards, in three languages |
Use it
kavach-pack new system.toml # a blank form with every option explained
kavach-pack build system.toml # writes governance-pack/<system>/
kavach-pack check system.toml # tier and gaps; exits 1 if there are blockers
check takes several forms at once, so a CI job can block a release when any AI system has unresolved blockers:
kavach-pack check ai-systems/*.toml
What is in the pack
| File | What it holds |
|---|---|
00-summary.md |
One page for the approver: tier, main reasons, blockers, decision needed |
01-risk-tier.md |
Seven factors scored 1 to 3; the highest sets the tier |
02-system-card.md |
Purpose, users, model, data, languages, limits and controls |
03-dpdp-checklist.md |
DPDP duties for this system, with section numbers, and every place personal data can hide (embeddings, caches, logs, agent memory, fine-tunes) |
04-vendor-questions.md |
Questions for the model provider, with what you already know filled in |
05-pre-launch-checklist.md |
Only the lines that apply at this tier, ticked where the form says they are done |
06-incident-plan.md |
Severity 1 events specific to this system, first-hour and 72-hour steps |
07-approvals.md |
Who approves at this tier, with sign-off rows |
gaps.json |
Every gap as data, for CI and dashboards |
How the tier is set
| Factor | Low (1) | Medium (2) | High (3) |
|---|---|---|---|
| Who sees the output | Internal team | Employees | Customers or the public |
| What the AI does | Drafts | Recommends; a human decides | Decides or takes actions |
| Personal data | None | Ordinary | Financial, ID, health, biometric or children's data |
| Domain | Productivity | Operations, HR, sales | Finance, health, legal, safety, credit, eligibility |
| Reversibility | Easy | Manual effort | Hard |
| Scale | Under 100 users | Up to 100,000 | Over 100,000, or vulnerable users |
| Languages | One, tested | Several | Several not tested, or none tested |
The highest factor wins: one high-risk factor makes the whole system high risk.
What the gap check looks for
Examples: no lawful basis or notice for personal data, erasure not tested across every store, unmasked logs, a vendor that may train on your data, unknown data location, quality or injection not tested in every supported language, no red-team for high-tier systems, agents without limits, human approval or a kill switch, and no incident owner, monitoring or rollback plan.
A blocker must be fixed, or formally accepted by the approver, before go-live. A warning should be fixed or explained. The same gap can be a warning at Low tier and a blocker at High tier.
The form
[system]
name = "Bank Support Assistant"
owner = "Head of Customer Service"
purpose = "Answers customer questions and can block a card or raise a dispute"
audience = "customers"
users = 2000000
[data]
personal_data = true
data_kinds = ["contact", "financial", "government-id"]
stores = ["vector-store", "cache", "logs", "agent-memory"]
[behaviour]
role = "acts"
domain = "finance"
actions = ["block card", "raise dispute"]
human_approval = "above-limit"
action_limit_inr = 25000
[languages]
languages = ["en", "hi", "or"]
quality_tested_languages = ["en", "hi"]
Run kavach-pack new for the full form, with every allowed value. JSON works too.
Limits
- Not legal advice. DPDP section numbers refer to the Digital Personal Data Protection Act, 2023. Confirm current obligations, the DPDP Rules timeline and sector rules (RBI, SEBI, IRDAI and others) with your legal team.
- The pack is only as good as the form. Ticked lines still need evidence.
- Sector-specific rule sets, such as RBI or SEBI guidance, are not built in yet. They are on the roadmap and will be added only after checking the official documents.
Related
- AI Governance Playbook: the templates this tool is built on
- Kavach-Eval: injection and data-leak tests in Indian languages
- Agent-Pariksha: reliability tests for AI agents that take actions
- Vismriti: DPDP consent and erasure for RAG and agents
- Nakli-Data: safe fake Indian personal data for testing
License
Apache-2.0
Metadata
Release files for ai-kavach-pack 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ai_kavach_pack-0.1.0.tar.gz | 23.6 kB | Without provenance | Details for ai_kavach_pack-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ai_kavach_pack-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for ai_kavach_pack-0.1.0-py3-none-any.whl |
Total release size: 50.0 kB
Release files / ai_kavach_pack-0.1.0.tar.gz
| Download URL | ai_kavach_pack-0.1.0.tar.gz |
|---|---|
| Size | 23.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5d2b8308b4e2cf269daff16f414c8480677a809d0460f071418a742b63245278
|
|
BLAKE2b-256 checksum How to use checksums |
7f0af949e6d4da75a1f049a27813abf19df8c55dceffb34020ac6069fcbebabd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / ai_kavach_pack-0.1.0-py3-none-any.whl
| Download URL | ai_kavach_pack-0.1.0-py3-none-any.whl |
|---|---|
| Size | 26.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
043deffe5b4a46d19278f44b47290aef8905db17a2392a8981448737be5a7146
|
|
BLAKE2b-256 checksum How to use checksums |
043126b6e3be225b6c28c3df31693ecd9363235003bb4e715b207775a3cfa269
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for ai-kavach-pack 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.