Focus area
Programmable closed-loop value
Rules that govern transactions between parties who don't share a ledger.
A rule-set language for value exchange among customers, merchants, and financial institutions. Stored value moves through the system according to constraints — not through a unified chain, but through an agreement graph.
Most of what people call "programmable money" is really programmable settlement — a smart contract that fires once the terms are agreed. The harder problem is programmable agreement: how do multiple parties, each with their own stored-value source, their own policies, and their own counterparty constraints, compose a single transaction that honors all of them?
The 2017 patent proposed a rule-set primitive. Each rule set associates two or more identifiers with a transaction. The rules dictate, limit, or control how the transaction executes. When rule sets conflict, a hierarchy picks the winner. That's it. Simple enough to reason about, expressive enough to cover customer + merchant + lender + loyalty + government-rebate in a single atomic event.
In 2026 those rule sets become smart-contract templates gated by verifiable credentials. The hierarchy resolver becomes a policy engine. The identifiers become DIDs or W3C VCs. The tenders become stablecoins, agent-initiated payments, and tokenized loyalty — but the mechanism of composition is the same. That's the bet the current work is built on.
Where it shows up
Three applications.
- 01
Split-payer healthcare checkout
Patient copay + HSA + insurer token + provider discount settling in one atomic transaction with a rule hierarchy resolving who pays first.
- 02
Multi-brand loyalty composition
Points earned at one property redeemable at another, with portfolio-level FX and liability management.
- 03
Disaster-relief disbursement
FEMA + state + insurer + employer + NGO rules each applied, conflict-resolved, and settled into a single household wallet without double-counting.
Related focus areas