Contract Approval with Legal Clause Validation

The problem

AI-reviewed contracts pass through Corules before countersigning. Required clauses are validated as present. Liability caps, payment terms, and indemnification limits are checked against authority thresholds. Contracts within policy auto-proceed to e-signature. Exceptions escalate to legal with the specific clause issue flagged.

Without deterministic enforcement, AI agents either block every edge case (adding manual overhead) or silently approve decisions that violate policy — with no audit trail to show auditors or regulators.

How Corules solves it

Corules sits between your AI agent and the action it wants to take. When the agent proposes a decision, Corules evaluates the full context against your compiled policy set in a single deterministic pass — no LLM, no ambiguity.

The result is a structured outcome: ESCALATE — liability_cap $10M exceeds max_liability_cap['vendor'] = $2M. Escalating to General Counsel.

Policy example

Corules policies are written in CEL (Common Expression Language). They are compiled once at publish time and evaluated deterministically at request time — no LLM, no variability.

// Contract approval policy (CEL)
context.indemnification_present == true
  && context.liability_cap <= params.max_liability_cap[context.contract_type]
  && context.payment_terms_days <= params.max_payment_terms_days
  && context.governing_law in params.approved_jurisdictions

This expression is evaluated against the structured context your agent sends in the /v1/validate request.

Integration options

Corules integrates with the tools your teams already use. All integrations call the same REST API or MCP server — your policy logic stays in one place.

Frequently Asked Questions