Documentation
The PASS protocol, in detail
How financial authority is expressed as a record, evaluated before an execution proceeds, and reported as a decision with a deterministic reason. Read in order for the argument, or go directly to the primitive you need.
Overview
- IntroductionWhat PASS is, the layer it occupies, and the vocabulary the rest of the documentation uses.
- The permission gapWhy keys, wallet permissions, protocol validation, application logic and model instructions each solve a different problem than a portable financial mandate.
- Core conceptsThe six primitives — Passport, Mandate, Policy, Adapter, Preflight and Decision — and how they compose.
- ArchitectureSystem structure, the path a proposed execution takes through it, and the trust boundaries it crosses.
Primitives
- PassportsThe credential primitive: issuers, subjects, credential types, validity, revocation and the privacy considerations that shape the model.
- MandatesMachine-readable financial authority: what an actor may do on behalf of a subject, expressed so that it can be evaluated rather than remembered.
- PoliciesThe rule categories a mandate is assembled from, and the difference between core enforcement and optional extensions.
Execution
- PreflightHow a proposed execution is normalized, evaluated against policy, and resolved into a decision before capital moves.
- AdaptersWhy arbitrary calldata cannot be trusted to describe itself, and how protocol-specific decoding produces validated policy inputs.
- AgentsOperating autonomous actors under a mandate: the division between decision-making and authority, and what that division buys.