2AYE
Guides, reference & supportCapability status

Documentation

How action authorization works

Follow signed intent, deterministic evaluation, exact-action approval, single-use grants and execution evidence.

Identity is the starting point

Authentication establishes who connected. A signed, immutable intent specifies what an agent may do, where, within which limits and until when. Registration alone creates no execution authority.

Evaluate the exact action

The canonical runtime evaluation accepts the registered predicate envelope. Missing required inputs fail closed. A model or risk score cannot convert a deterministic denial into permission. Material amount, currency, merchant, resource and environment bindings must remain unchanged.

Ask a person only when required

Routine actions may proceed within current signed authority when all policy checks pass. Required approval covers the exact action; it cannot expand a hard limit or rewrite signed authority. Changing material terms requires valid new authorization.

Enforce where the action happens

A short-lived, single-use grant is checked at the protected destination or its configured gateway. The receiver must check current authority, exact parameters and replay before executing. An ALLOW result is permission to attempt execution, not proof of success.

Your governed workflow

Bring the next consequential action under control.

Show us the actor, protected resource, and action that must never execute without exact authority. We’ll map the decision and evidence path with you.

Discuss your workflow Read the implementation guide
How action authorization works | 2AYE Documentation