Coherence Engines
Additive runtime governance

Compliance Reflex

Your existing Coherence runtime stays authoritative. Compliance Reflex adds a simple enforcement layer on top: ALLOW, LIMIT, REPAIR, REVIEW or BLOCK — with a reason, recommended fix and metadata-only evidence receipt.

Request failed with status code 404

Proof boundary: this layer enforces configured technical policies. It does not certify that an organization is legally compliant with GDPR, the EU AI Act or another law.

ALLOW

0

Allowed

LIMIT

0

Allowed with limits

REPAIR

0

Repair / reroute

REVIEW

0

Human review

BLOCK

0

Blocked

Reflex checks recorded

0

Latest 500 metadata-only receipts

Routeable providers

0

Blocked

0

Human reviews

0

Sovereignty Mode

Extra routing constraints added on top of the existing provider/runtime controls.

Global: No extra geographic restriction. Existing Coherence governance remains active.

Policy Packs

Composable technical controls. These add to, not replace, existing Coherence governance.

Execution chain

Existing Coherence runtime → Compliance Reflex → ALLOW / LIMIT / REPAIR / REVIEW / BLOCK → existing provider runtime → postflight → evidence receipt.

Governed provider metadata

Only metadata already stored for your provider connections is shown here. Credentials are never returned.

ProviderConnectionHosting regionResidencyGovernance metadata

No routeable providers found. Configure and test a provider in Provider Connections.

Recent Compliance Reflex receipts

Why a request was allowed, limited, repaired, reviewed or blocked.

No Compliance Reflex runtime receipts yet. They will appear automatically when governed AI requests are processed.