Prevent AI Agent Policy Violations Before They Execute

The answer

The key insight is that violations must be caught before execution, not discovered in post-hoc audit. Corules provides two evaluation gates: Gate 1 (constraints) tells the AI what it is allowed to propose before it reasons. Gate 2 (validate) confirms the final decision before execution. Between these two gates, the AI cannot produce an action that violates policy — because non-compliant decisions never reach the execution layer.

How it works

Corules's policy runtime sits in the enforcement path between your AI agent and the action it wants to take. The agent sends a structured context payload to /v1/validate. Corules evaluates the context against a compiled CEL policy set and returns a structured decision — ALLOW, BLOCK, or ESCALATE — with a reason and audit ID.

Every decision is recorded in an immutable audit ledger. You can replay any past decision by providing the policy_set_version and the normalized input hash — the result will be identical.

Policy example

Policies are written in CEL (Common Expression Language). They are compiled once at publish time and evaluated in microseconds at request time.

// Gate 1: what is the AI allowed to propose?
// Called before AI reasoning begins
GET /v1/constraints → { max_discount: 0.25, required_fields: [...] }

// Gate 2: is this specific decision compliant?
// Called before execution
POST /v1/validate → { outcome: "BLOCK", violation: "discount_pct > 0.25" }

Frequently Asked Questions