Propose: Stored Value / Credit
On-behalf-of: Ben Stull <ben.stull>
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
---
|
||||
slug: stored-value
|
||||
title: Stored Value / Credit
|
||||
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
|
||||
---
|
||||
|
||||
Stored Value is the root money concept the ecommerce platform's credit model hangs on: value a Human has loaded and now holds on the platform, deliberately constrained — not cashable, not transferable out, and explicitly not a stablecoin. The constraint is not incidental; it *is* the definition, and it must be defined in relation to the Human whose money it is. Removing cash-out closes the redemption-fraud vector and the money-transmission trigger — but it also removes an exit the Human would otherwise have, so the concept must hold that tension in the open rather than hide it behind 'store credit.'
|
||||
|
||||
Establishing Stored Value as a first-class OHM entity lets every downstream mechanic — Load, Settlement, Discount, Breakage, Float — cite one contestable definition of 'what the balance is' instead of each re-deriving it. It serves Agency (the Human's own money, with its exit deliberately removed) and Temporality (a balance persists, and a person's relationship to it changes over time). It is also where OHM broadens to hold a commerce noun, defined in service of the Human rather than the ledger.
|
||||
|
||||
Reference in New Issue
Block a user