Standards
Recur Labs publishes a small set of standards. RIP-100 defines the foundational authorization primitive; RIP-001 and RIP-002 define a profile and registry infrastructure that consume it.
RIP-100 — Authorization Objects
Defines Authorization Objects (AO): first-class, time-bounded, revocable authorizations that exist independently of execution.
RIP-001 — Permissioned Pull Standard
A standard for expressing authorization as an explicit object, decoupled from execution, enabling pull-based flows across digital systems.
RIP-002 — Consent Registry
A registry model for recording and observing authorization objects. Intended as an extension to RIP-001, not a replacement.
Derived standards
These proposals describe system-level consequences implied by the core Recur primitives. They are not foundational, but follow directly once authorization is explicit machine state.
RIP-011 — Pull-Secured Account
A minimal custody container whose structure is implied once authorization exists as explicit, time-bounded machine state. Value may only move via permissioned pull execution.
Design constraints
- Authorization must be explicit (as an object), inspectable, and revocable prior to execution.
- Non-action is a valid outcome (authorization may remain unused).
- Execution systems should consume authorization objects, not define them.