Compliance Oracle · Live
This is not a brochure and not a mock. Every button below runs the real Compliance Oracle: a subject, their verified credentials, and a versioned rule pack in — a binary ALLOW / DENY verdict out, with machine-readable reasons and a tamper-evident decision seal. The engine blocks first and asks never: a clearance is granted only when every rule explicitly passes. A missing or expired credential, a jurisdiction it can't establish, an unrecognized rule kind, or an empty policy each fail closed to DENY — never silently skipped, never an accidental yes. The exact policy applied is pinned by its SHA-256 hash, and every verdict carries a seal that breaks on any later edit. Pure logic; no keys, no network, no funds move.
An investor must be cleared before they may subscribe to an offering. The policy requires four facts: a valid KYC credential, a sanctions-clear credential, an accredited-investor credential, and an allowed jurisdiction. Each "Run it" button presents a different real set of credentials or policy — the engine, not this page, decides the verdict.
| Field | Value | Role |
|---|---|---|
| investor:acme-capital-7741 | Wants to subscribe to an offering | Subject |
| FAS-CLEARANCE-7741 | action: subscribe_offering | Request |
Raw engine JSON (verdict + machine-readable reasons + per-rule results + pinned policy hash + tamper-evident decision seal)
Runs the real Compliance Oracle — blocks first, asks never; every verdict carries a tamper-evident seal. The exact policy is pinned by its SHA-256 hash, so two different rule packs produce two different verdicts you can prove apart. Pure logic; no funds move. Want the production oracle wired to your own credential issuer, rule packs, and audit log? Talk to us →