🔒All inputs are processed locally in your browser. Nothing is transmitted, stored, or logged. Inputs disappear when you close the tab.

OCG-Industries Showcase · Cluster ⑥ Payments and Financial Infrastructure

Mandate Audit
Chain

When an agent moves money, the question that follows is what it was allowed to do. Enter the mandate identifier, the scope it was granted, the spend ceiling it carries, and the action the agent actually attempted, and this tool decides whether that action was inside the authority on record and stamps the decision. The check is a set membership test and an integer comparison, nothing more, which is exactly why the answer reproduces. Re-running the same mandate and the same attempted action returns the same verdict and the same hash, so authority can be cited after the fact instead of reconstructed from memory.

Data vintage: 2026

Inputs STEP 1
A system identifier. No personal names.
Comma separated, for example PURCHASE,REFUND,SUBSCRIBE
--
--
In Scope
--
Attempted action matches a granted scope token
Within Ceiling
--
Attempted amount at or below the spend ceiling
Headroom
--
Ceiling minus attempted amount, in cents
Detail
Mandate identifier--
Agent identifier--
Granted scope--
Attempted action--
Spend ceiling--
Attempted amount--
Denial reason--
Audit key--
Policy Mandate v2.0 · what is this?