OpenChainGraph Suite · ART-703

Mandate Authorization Gate

An agent proposes a payment; a deterministic ten-rule check against the mandate decides. On authorize the node issues a one-use authorization bound to the exact request digest, with a short validity window. At commit time a second mode verifies the committed request against that authorization. Every rejection names the failing rule. No human step.

Approval GateOne-Use AuthorizationCommit VerificationInteger Minor UnitsZero PIIClient-side only
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data; use synthetic or anonymised inputs only.
Scope & reliance
Authorize mode evaluates a fixed ten-rule order and lists every failing rule; the first is the primary reason. The issued authorization is bound to the exact request digest and mandate digest, valid from as_of to as_of + ttl (1 to 900 s, clipped to the mandate expiry), and its authorization_id doubles as the rail's single-use nonce (0x-prefixed 32-byte hex). Verify_commit recomputes the id, re-digests the committed request and checks the window. Amounts are integers in minor units; the mandate cap converts by integer string arithmetic through a curated minor-unit exponent table (an unknown currency is refused, an over-precise cap is refused, never rounded). Timestamps are UTC with a trailing Z only. Declared exclusions: single use is enforced by the payment rail through the nonce, not by this stateless node; budget state is caller-supplied (spent_minor); the mandate signature is not verified here, that is art-01 or art-31's job; an absent rail allowlist allows no rail. This node ships compute_proof_ready: deferred; proving is async queue work, not a per-wave gate.
Mandate, state and proposed payment
Edit any field and run. The sample is the clean authorize from the build spec; the commit demo presents its authorization back inside the window; the reject demo exceeds the per-payment cap.
Result
Proof status
This node ships compute_proof_ready: deferred: the decision above is a deterministic, reproducible function of the declared inputs (the same kernel runs server-side and inside this page), and a zkVM compute-integrity proof is queued as async follow-up work.
Execution Hash & §4 Artifact
SHA-256 execution hash (JCS canonical, RFC 8785):