Working category concept

Proof of Authority

A portable, independently verifiable claim demonstrating that an agent’s specific action falls within a valid chain of delegated authority, satisfies applicable constraints, and has an attributable outcome.

Proof of Authority is a working category concept. It is not a new cryptographic primitive and it is not an industry standard. EXOCHAIN normative specification v2.2 and the beta v0.2.7 release describe the current software. They do not freeze this category name as a completed receipt format.

What the claim has to carry

The intended portable receipt binds the parties, the limits, the evidence, the action, the outcome, and revocation. These fields are the category’s contents. They are not a published interoperability profile.

Principal

The human or institution that holds the original authority

Delegate

The agent or operator acting under that authority

Scope

The decisions and actions the delegation allows

Constraints

Limits that still apply, including amount, purpose, and policy

Decision evidence

The record the actor relied on for this action

Action

The specific act being authorized or attested

Outcome

What occurred after the action was taken

Revocation state

Whether the delegation was still valid at the time

Pieces already in the beta

Bailments, consent, revocation, governance, and trust receipts are the conceptual pieces EXOCHAIN already implements in beta. The work is to expose them as a developer primitive other stacks can call without adopting the entire constitutional architecture.

Trust receipts · Autonomous Volition Credentials · Two-call developer experience

Talk to us about a design-partner pilot.

Bring one constrained, cross-organizational workflow — a procurement decision or an executive approval, for example — where two parties need to verify legitimate authority without sharing an internal system. Developers can start from the SDK in the public repository.