Supplier Onboarding with Multi-Stage Compliance Validation

The problem

New supplier onboarding requests are gated through multiple Corules evaluation steps. Stage 1: basic documentation (W9, insurance certificate). Stage 2: sanctions screening and adverse press. Stage 3: risk-tier routing — low-risk auto-approves to preferred status, high-risk escalates to procurement leadership. Every onboarding decision is logged with document hashes and verification timestamps.

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: BLOCK — on_sanctions_list = true. Supplier onboarding blocked. Manual review required.

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.

// Supplier onboarding policy (CEL)
context.w9_present == true
  && context.insurance_cert_current == true
  && !context.on_sanctions_list
  && context.financial_stability_score >= params.min_financial_score

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