Recur Labs logo
Recur Labs
Open standards for authorization-centric digital systems.
Authorization should be first-class.
Recur develops interoperable standards that treat authorization as an explicit object, separate from execution. Permissions should be time-bounded, inspectable, and revocable prior to action.
Read the standards Research paper
Principle: Execution should never imply authorization.
Standards
Recur focuses on a small number of foundational standards. Everything else is exploratory and non-normative.
RIP‑001 · Permissioned‑Pull Standard Stable
Defines permissioned pull as a first-class authorization primitive: explicit, time-scoped, revocable permission that may be exercised later under constraints. Execution becomes downstream settlement.
RIP‑002 · Consent Registry Draft
Defines a registry model for recording and observing authorization objects. Enables verifiable authorization state without coupling to execution systems.
Out of scope
Recur Labs does not define products, user interfaces, economic policy, governance systems, or application-level business logic. These concerns are intentionally left to implementers.
Participation
Recur Labs is an open standards effort. Discussion, critique, and independent implementations are encouraged.