OPEN MACHINE AUTHORITY SPECIFICATION

Authority infrastructure for machines that can act.

PMAS defines how delegated Machine Authority is expressed, attenuated, evaluated, revoked and proven across autonomous agents and commerce systems.

1.0 RC1 current candidateOpen technical specificationPaylogee reference implementation
Authority activePMAS 1.0 RC1
PrincipalAcme Corporation
AgentProcurement Agent 07
Maximum transaction$2,500
Allowed actions
purchasequote.accept
Rails
x402virtual_card
Approval above$750
No Authority AmplificationPASS
01
BOUND

Authority Envelope

Express actions, resources, counterparties, environments, rails, budgets, validity, delegation and state as explicit machine-verifiable limits.

02
ATTENUATE

No Authority Amplification

Every child delegation must be equal to or narrower than its parent. Empty scopes grant no authority; only explicit wildcards are unbounded.

03
PROVE

Portable Proof

Bind delegated authority, canonical decisions and evidence to Paylogee Machine Authority Proof and Commerce Receipt systems.

AUTHORITY LIFECYCLE

One contract from delegation to evidence

PMAS separates intent, authority and execution so no transport or rail can silently become an authority source.

01Identify
02Delegate
03Constrain
04Evaluate
05Approve
06Execute
07Prove
SCHEMA LIBRARY

Release candidate artifacts

Specification details →
REFERENCE IMPLEMENTATION

PMAS is open. Paylogee enforces it.

The specification defines portable authority semantics. Paylogee’s Machine Authority Kernel binds those semantics to KYA, delegation, policy, approval, execution rails, proof and Commerce Receipts.

MCP · A2A · x402 · Virtual CardPMAS Action RequestMachine Authority KernelUniversal Authority GatewayAPPROVE · REQUIRE_APPROVAL · DECLINE