kailash-pact 0.12.0

PACT governance framework — D/T/R accountability grammar, operating envelopes, knowledge clearance, and verification gradient for AI agent organizations

kailash-pact

PACT governance framework — D/T/R accountability grammar, operating envelopes, knowledge clearance, and verification gradient for AI agent organizations.

Part of the Kailash enterprise AI platform.

Quick Start

from pact.governance import GovernanceEngine

engine = GovernanceEngine.from_yaml("my-org.yaml")
verdict = engine.verify_action("D1-R1-T1-R1", "write_report", {"cost": 50.0})

if verdict.allowed:
    print("Approved:", verdict.reason)
else:
    print("Blocked:", verdict.reason)

Installation

pip install kailash-pact

With Kaizen agent integration:

pip install kailash-pact[kaizen]

Features

• D/T/R Grammar Engine — Accountability grammar (Department/Team/Role) with positional addressing
• Three-Layer Envelopes — Role (standing) + Task (ephemeral) = Effective (computed intersection)
• Knowledge Clearance — Five-level classification independent of authority/seniority
• 5-Step Access Enforcement — Clearance → Classification → Compartment → Containment → Deny
• GovernanceEngine — Single facade composing all primitives
• PactGovernedAgent — Wrap any Kaizen agent with governance enforcement
• SQLite/PostgreSQL Stores — Persistent governance state
• REST API — 9 governance endpoints with auth and rate limiting
• CLI — kailash-pact validate org.yaml

Documentation

• Quickstart — Zero to governance in 10 minutes
• Architecture — How it all fits together
• Vertical Guide — Build your own governed platform
• API Reference — REST endpoints
• Cookbook — Common patterns
• YAML Schema — Org definition format

Cross-SDK Conformance (PACT N4/N5)

The PACT N6 cross-SDK conformance contract pins byte-for-byte canonical JSON across language SDKs. The Python implementation lives in pact.conformance and drives the same vector files the Rust SDK does.

Run the runner programmatically

from pact.conformance import ConformanceRunner, load_vectors_from_dir

vectors = load_vectors_from_dir(
    "/path/to/kailash-rs/crates/kailash-pact/tests/conformance/vectors"
)
report = ConformanceRunner().run(vectors)
if not report.all_passed:
    raise SystemExit(report.render_failure_report())
print(f"PACT conformance: {report.passed}/{report.total} passed")

Run via pytest

The Tier 1 unit tests at tests/unit/conformance/test_runner.py::test_runner_passes_against_real_cross_sdk_vectors auto-discover the kailash-rs sibling checkout and exercise every vector. The test SKIPS gracefully when the sibling repo is absent, so unit-only CI hosts do not fail.

pytest packages/kailash-pact/tests/unit/conformance/ -v

Vector schema

Each vector is a JSON document at crates/kailash-pact/tests/conformance/vectors/ with:

• id: unique identifier (sort key)
• contract: "N4" (TieredAuditEvent canonicalisation) or "N5" (Evidence canonicalisation)
• input.verdict: {zone, reason, action, role_address, details}
• input.posture: required for N4 (PseudoAgent, Supervised, SharedPlanning, ContinuousInsight, Delegated)
• input.fixed_event_id / input.fixed_timestamp: required for determinism
• expected.canonical_json: the byte-for-byte JSON the SDK MUST emit
• expected.tier / durable / requires_signature / requires_replication: optional N4 invariants

The runner compares actual vs expected via byte equality (NOT JSON-equal); a single-byte drift surfaces as a FAILED outcome with both SHA-256 fingerprints populated for forensic correlation.

License

Apache 2.0 — Terrene Foundation