AI Governance Control Plane
Observe. Evaluate. Govern. Replay.
Hover a plane to trace its live exchange. White orbit: one complete execution.
Make every AI action
legible before it lands.
KAVACH turns AI execution activity into governed, explainable records as the system operates.
Decision twin
A flight deck for every execution.
Every execution becomes a live decision surface where signals, policies, evidence and outcomes remain connected.
Hover a layer to bring its decision stream forward.
01 / Replay
Replay the evidence, not the incident.
KAVACH turns a past execution into a governed reproduction. The original remains intact; the replay becomes new evidence with explicit lineage.
02 / Ontology
Lineage stays alive.
Governed assets are not isolated records. Their versions, evidence, policies, and decisions remain connected in a graph you can inspect at any time.
Nodes glow. Edges light. Evidence stays connected.
03 / Evaluation
Measure what the system is becoming.
Live evaluation turns model behavior into metrics you can compare, review, and attach to governance decisions before a regression becomes production reality.
04 / Intelligence
Let the system recommend the next control.
KAVACH reads trend and drift signals across governed executions, then returns actionable recommendations to the people operating the system.
Suggested policy change
Require groundedness ≥ 0.85 for the support-agent production route.
Drift review recommended
Confidence is stable; groundedness variance is rising across the latest 14 runs.
Architecture
Layered Control Plane for AI Governance
KAVACH separates experience, control, governance, execution and persistence into explicit planes with unidirectional data flow.
Capabilities
Core Governance Building Blocks
Each subsystem is independently deployable and exposed through REST APIs and MCP tools.
Job Execution Control Plane
Record and execute long-running governance work — evaluations, experiments, replay, and drift analysis — with durable lifecycle tracking.
Evaluation Plane
Turn workflow outputs into evaluation results using pluggable providers. Providers sit behind contracts, not platform boundaries.
Governance Ontology
A semantic graph describing relationships between governed assets — prompts, models, datasets, decisions, and evidence.
Governance Decisions
Explainable, auditable outcomes generated from evidence and policy. Trace lineage from decision back to every supporting artifact.
MCP Server
Expose governed read and controlled-write operations to agents through auditable MCP tools, each delegating to one REST endpoint.
Settings Control Plane
Typed configuration with SYSTEM, ORGANIZATION and PROJECT scopes. Compare-and-set updates with versioned audit trails.
Audit & Replay
Capture workflow and node-level execution records. Reconstruct historical executions for investigation, debugging and governance review.
Drift Analysis
Compare evaluations over time, calculate drift and produce governance-oriented artifacts from historical data.
Replaceable Persistence
SQLite for local development, PostgreSQL for production, Snowflake for analytics. Repository contracts keep storage interchangeable.
Principles
Engineering Principles
KAVACH is built to be operated in production. These constraints shape every interface.
Control Plane Ownership
Kavach owns governance state and decisions. It tracks assets, results, comparisons, rankings and recommendations — but never the live AI runtime or deployment system.
Explicit Contracts
Every boundary is visible in code. Repository interfaces, provider interfaces and framework-neutral APIs are all explicit contracts. Hidden cross-system contracts are avoided.
Immutable Artifacts
Governed records are immutable where possible. Mutable control flows create new records or versions instead of mutating historical facts.
Version Everything
Prompts, models, datasets and experiment-facing artifacts are versioned. Versioning is required for reproducibility, comparison, auditability and replay.
Replayability
If a governance decision cannot be reconstructed later, it is weak evidence. Replayability affects storage, versioning, immutability and API design.
Storage Independence
The platform does not depend on SQLite as a core architectural choice. Repository contracts preserve the ability to add PostgreSQL, Snowflake or other stores.
Provider Independence
Evaluation logic remains behind provider interfaces. TruLens is the current implementation, but the architecture should not require provider-specific knowledge.
Failure Isolation
Failures stop at the narrowest useful boundary. A provider failure should not silently mutate registry state. A transport adapter should not rerun ranking logic.
Interfaces
Evaluate Governance Decisions
The same governance operation is available over REST and as an auditable MCP tool. Every call is correlated and recorded.
POST /api/v1/decisions/evaluate
{
"subject_type": "agent_execution",
"subject_id": "execution-2048",
"policy_id": "production-ai-policy",
"evidence_ids": [
"eval-result-981",
"audit-event-477"
]
}
// 200 OK
{
"decision_id": "decision-991",
"outcome": "APPROVED",
"policy_version": "v1",
"reason": "All mandatory controls satisfied"
}Releases