The Policy Constitution for Governed AI.
CAES defines how decisions are enforced. CPP defines how decisions are determined. Together, they make AI execution reviewable, replayable, and policy-bound.
Policy without a standard is not governance.
Without CPP, policy remains application logic, prompt convention, or mutable configuration. It can be claimed, changed, and argued about — but it cannot be proven.
With CPP, policy becomes a deterministic artifact that can be hashed, replayed, audited, and bound into receipts. The policy hash is the checksum of governance itself.
CPP applies to all policy systems used to evaluate execution actions, behavioral outputs, data operations, and any output crossing a CAES Effect Boundary.
CPP, CAES, and the Receipt form one chain.
Defines deterministic, versioned, immutable, hashable policy semantics. Produces the PolicyHash bound at evaluation time.
Requires a valid Decision Receipt before any governed action crosses an Effect Boundary. Fail-closed on absence.
A cryptographically signed artifact containing the PolicyHash. Independently replayable and offline-verifiable.
Six non-negotiable properties.
Identical inputs produce identical outputs. No stochastic evaluation paths.
LLM-only or probabilistic authorization paths.
Every policy instance must carry a version identifier. Versions must be immutable.
Ambiguous policy identity and undetectable version drift.
Updates must produce a new policy version. No in-place modification.
Silent retroactive policy changes and audit gaps.
Every policy instance must produce a canonical PolicyHash: SHA-256 over the canonicalized policy. Same inputs always produce the same hash.
Undetectable policy tampering and non-reproducible audits.
Rule evaluation must be traceable. Matched rules must be explicitly recorded in evaluation output.
Black-box policy outcomes and unverifiable authorization claims.
Policies must be evaluable outside the originating system. Offline verification must be possible.
Vendor-locked governance and offline-verification failure.
The cryptographic fingerprint of governance itself.
Every CPP-compliant policy must produce a deterministic hash bound to the policy state at evaluation time:
Verifier can recompute this offline — no network call required.
Without PolicyHash, audits become interpretive, policy drift becomes invisible, and decisions become non-reproducible.
Mandatory for Level 2 and Level 3 conformance.
CPP enables PolicyHash binding, deterministic audit, offline verification, and cross-system governance portability. These are required properties for CAES Level 2 conformance.
Explicitly prohibited patterns.
CPP is a companion to CAES, not a standalone thesis.
CAES defines the structural requirements for governed AI execution. CPP defines the policy substrate that CAES Level 2 and Level 3 implementations must use. Read them together.