the base does not choose your money
The catalog at the root of this design had an easy option: name a unit of account and be done. The record declines. The platform is described as currency-agnostic — payment is declared by contract, so one catalog carries many payment models, and a participant settles under whichever one its own agreement names. The base stores the agreement, never the money.
The tension is coherence against portability. One unit makes every price comparable and every settlement a single subtraction. Many units mean the design cannot state what anything costs in a common measure, and the coordination that a shared number quietly provides has to be rebuilt by whoever needs it.
The harder half is the exit. Because the unit is a declaration rather than a foundation, the record specifies a route by which the whole network can move to a different one if the chosen unit fails or becomes unsuitable — a change at the level of the catalog, not a rewrite of the layers beneath. A monetary choice that cannot be unmade is a permanent bet placed by people who will not be present when it resolves.
What it costs is a single price signal the design does not have, a compatibility burden at every boundary where two payment models meet, and the admission in writing that the designers do not know which unit will hold. What it proves is that the economic commitment was made reversible in the same document that made it — the discipline most designs skip, because reversal looks like doubt.
drawn from: framework and changelog
Every note carries a codename and one idea. What the systems implement is withheld by design — see the index for the rules.