Parent Authority
Paste the authority the first agent currently holds. This is the maximum boundary available to delegate.
The PMAS verifier proves that authority cannot grow as it moves between machines. Compare what a parent agent holds with what it proposes to delegate downstream.
You do not need to be a PMAS expert to understand the result. The JSON is the technical artifact; the verifier translates it into a clear delegation comparison.
Paste the authority the first agent currently holds. This is the maximum boundary available to delegate.
Paste the authority the downstream agent would receive. It may stay equal or become narrower.
Paylogee compares scope, amounts, merchants, environments, rails, currencies, validity, state, usage and subdelegation.
PASS means no authority grew. REJECTED means the child gained authority it was never entitled to receive.
The example below is intentionally simplified for business users. The JSON editors later on show the portable PMAS representation.
Each layer answers a different enterprise question. The verifier focuses only on whether delegated authority grew.
Machine identity and subject.
Identity, principal and runtime posture.
Bounded operational power.
Portable authority contract.
This verifier answers no.
Canonical governance and decision path.
Post-action evidence.
Use the canonical examples or paste your own documents. The left side is the authority being delegated from; the right side is the authority proposed for the child.