- action
- deploy sha256:a91e…
- audience
- release-service / prod
- authority
- root → team → release-agent
- constraints
- canary · before 14:32 UTC
Permission,
resolved.
Auths Proof turns a chain of delegated authority into one deterministic result: an exact action that is authorized—or a precise reason it is not.
The verifier gets facts.
Not policy theater.
A verifier receives the proof, the proposed action, and explicit trusted context. It validates signatures, walks delegation, intersects constraints, and returns a sealed result without discovering identity or calling a control plane.
Take explicit inputs
Proof bytes, action bytes, time, trusted roots, and verification limits enter together.
Walk authority
Each delegation must be valid, in scope, unexpired, and no broader than its parent.
Seal the action
The action digest, audience, and effective constraints become one verified result.
Explain the decision
Consumers receive stable success data or a structured, deterministic failure.
Identity-agnostic
Bring any principal system that can establish control of a signing key. Authority remains a separate concern.
Protocol-defined
Canonical encoding and verification semantics belong to the public contract, not one hosted service.
Adversarially bounded
Depth, bytes, objects, and cryptographic work are limited before untrusted input is accepted.
Conformance-ready
Golden vectors, negative fixtures, and fuzz targets keep implementations in exact agreement.
Verify. Decode. Execute.
The verified action—not ambient credentials or unchecked request data—becomes the command.
// No network. No hidden state.
result = proof.verify(
envelope,
proposed_action,
trusted_context
)
if result.authorized:
execute(result.verified_action)Make authorization inspectable.
See how explicit trust, bounded delegation, and exact actions form one portable authorization model.