RIP-100 — Authorization Objects
Draft
Foundational primitive for explicit, time-bounded, revocable authorization objects that exist independently of execution.
Standards Lab
Open standards for authorization-centric digital systems.
Recur Labs develops interoperable standards that treat authorization as a first-class object, explicitly separated from execution.
Core principle
Execution should never imply authorization.
Scope
Authorization primitives and registries — not products or economics.
Standards
Recur focuses on a small number of standards: a foundational authorization primitive, plus optional profiles and infrastructure.
RIP-001 — Permissioned Pull
Stable
A financial authorization profile for Authorization Objects, enabling permissioned pull without coupling consent to settlement timing.
RIP-002 — Consent Registry
Draft
Registry infrastructure for observing, verifying, and revoking Authorization Objects without defining execution semantics.
Out of scope
- Application-level products and user interfaces
- Economic policy, incentives, or governance design
- Business logic above authorization validity
- Marketing narratives or claims of inevitability
Participation
Recur Labs is an open standards effort. Discussion, critique, and independent implementations are encouraged.
If you maintain a public repository for RIPs, add your links in About.