Propose: Closed- vs Open-Loop Classification

On-behalf-of: Ben Stull <ben.stull>

rfcs/float.md

@@ -0,0 +1,19 @@
+---
+slug: float
+title: Float
+state: super-draft
+id: null
+repo: null
+proposed_by: ben.stull@wiggleverse.org
+proposed_at: '2026-06-01'
+graduated_at: null
+graduated_by: null
+owners:
+- ben.stull
+arbiters: []
+tags:
+- payments
+---
+
+Float is the pool of outstanding prepaid balances the platform holds and can earn yield on — other people's money, held in trust. This RFC defines Float with the safeguarding rule built in: the float is protected, holders are not paid interest, and it is never lent out. It serves custody and Dignity, and pairs with Platform Sustainability and Breakage.
+

rfcs/loop-classification.md

@@ -0,0 +1,19 @@
+---
+slug: loop-classification
+title: Closed- vs Open-Loop Classification
+state: super-draft
+id: null
+repo: null
+proposed_by: ben.stull@wiggleverse.org
+proposed_at: '2026-06-01'
+graduated_at: null
+graduated_by: null
+owners:
+- ben.stull
+arbiters: []
+tags:
+- payments
+---
+
+Whether stored value is clean store credit or a regulated money-transmission instrument turns on a single line: does value move only among commonly-owned storefronts, or between unaffiliated owners? This RFC defines that closed- versus open-loop classification, keyed to common ownership rather than storefront count. It documents the regulatory line the two-tier model rests on — it does not clear it, which remains a legal matter for counsel.
+