Gate criteria scope which data an agent may access or export; the signed decision record captures the exact action context presented to the approver.
AIUC-1 · July 15, 2026
Human approval evidence for consequential agent actions.
Permission Protocol sits at the action choke point. It records what crossed a customer-defined gate, who approved or denied it, and the exact payload they reviewed.
Receipts bind the requesting agent ID and run context to the authorization decision. The customer's IdP remains the identity source.
The gate policy enumerates which agent capabilities require a named human signature before execution.
Infrastructure and code actions are gated at the irreversible call, with the payload or artifact hash bound to the signed decision.
C007.1 is the customer's gate criteria document. C007.2 is the gate policy defining which actions require a signature. C007.3 is the approval queue, signed decision record, and decision-latency report.
Restricted tool calls fail closed until policy clears them or a named human signs. Denials are recorded as first-class evidence.
A signed decision names the accountable approver for the exact action payload they reviewed.
Every routed decision produces a portable record containing the agent, action, policy result, signer or policy approver, timestamp, and input hash.
Boundary: thresholds are recorded, not enforced by packs
Permission Protocol records what crossed the customer's threshold and the decision it triggered. Server-side threshold enforcement is not live: policy packs return 409 PACKS_NOT_ENFORCED. During a pilot, threshold logic stays in the customer's wrapper at the choke point.
PII is anchored on A003.1 data access scoping. Infrastructure and code are anchored on B006. We do not rely on retired E007 or on retired A006 core authentication/authorization claims; A006.2 DLP may be supplemental where the customer operates it.
C007 crosswalks
NIST AI RMF GOVERN 3.2 / MAP 3.5 · CSA AICM GRC-15 · OWASP Agentic ASI09
Scope one gateStandards we map to
Permission Protocol implements approval-gate controls and produces the evidence these frameworks ask for. It is not a conformance target, and this site does not claim conformance. The receipt format each mapping relies on is an open specification.