Loading Gate demo…
How It Works
Four steps from request to receipt. No step can be skipped.
Agent submits a request
A purchasing agent asks to pay a vendor. The request includes amount, recipient, agent type, and reasoning.
Policy cascade evaluates
Seven rules run in strict priority order. The first matching rule decides the outcome. If nothing matches, the default is blocked.
Human reviews (when required)
Transactions that exceed agent authority are escalated — never silently approved. Approvals expire; there is no auto-approve.
Evidence pack is sealed
A SHA-256 receipt captures the request, evaluation, and decision. The hash is generated server-side and cannot be altered by the client.
Fail-Closed Doctrine
The Gate refuses power it hasn't earned the right to exercise. Four principles govern every evaluation.
Default is blocked
If no rule explicitly authorizes a transaction, it is denied. There is no implicit allow.
Errors fail safe
If the policy engine throws an exception, the verdict is blocked — not a retry, not a pass-through.
Humans approve, never agents
Escalated transactions require a human decision. Approvals expire after 72 hours; the system never auto-approves.
Every decision has a receipt
SHA-256 evidence packs capture the full decision chain — request, rules evaluated, verdict, and approval (if any).
Built On
Same stack and governance patterns used across Truvesta, Ardura, and Equira — applied to a single, auditable flow you can test yourself.
Pure-function policy engine
Server-side evidence generation
Client-side cascade animation
Stateless receipt API
This is a simulated demo with deterministic scenarios. No real payments are processed. The policy engine and evidence packs are fully functional.
Book a Deep-Dive →