Skip to main content

Approval Requirements

Approval requirements gate operations behind multi-party authorization. These are distinct from confirmations — approvals require a different person or role to authorize.

Declaration​

<button
  axag-intent="refund.process"
  axag-entity="refund"
  axag-action-type="write"
  axag-risk-level="high"
  axag-confirmation-required="true"
  axag-idempotent="false"
  axag-approval-required="true"
  axag-approval-roles='["finance_manager","finance_director"]'
  axag-approval-count="1"
>Process Refund</button>

Approval Model​

  • axag-approval-roles — Roles authorized to approve
  • axag-approval-count — Number of approvals required (default: 1)
  • The invoking agent/user cannot self-approve

Agent Runtime Behavior​

When axag-approval-required="true", agent runtimes MUST:

  1. Submit an approval request rather than executing directly
  2. Notify the appropriate approval roles
  3. Wait for the required number of approvals
  4. Execute only after all approvals are received

Server Enforcement​

An agent can skip these steps, so the server MUST refuse an approval-gated call that has no approval, with AXAG_APPROVAL_MISSING. @web-axag/server does this on every call through an approvals hook you provide — it answers whether this call, by this actor, has been approved. How requests are raised, routed to approval_roles and counted is up to your application; approval_count isn't carried into the manifest in 1.1, so the hook is where it is enforced. See Safety Enforcers.