PLAN
Assets
The ledger is multi-asset by construction. Every asset that settles here, with the precision a caller needs to read its amounts.
| Asset | Symbol | Class | Decimals | In circulation | State |
|---|---|---|---|---|---|
| Flashy Gold | FG | REWARD_CURRENCY | 2 | 225 426.10 | ✓ RECONCILED |
| Flashy Work Unit | FWU | COMMODITY_UNIT | 0 | ——— | ∅ UNAVAILABLE |
| Wheat | WHEAT | COMMODITY_UNIT | 0 | ——— | ∅ UNAVAILABLE |
| Wood | WOOD | COMMODITY_UNIT | 0 | ——— | ∅ UNAVAILABLE |
| Stone | STONE | COMMODITY_UNIT | 0 | ——— | ∅ UNAVAILABLE |
| Iron | IRON | COMMODITY_UNIT | 0 | ——— | ∅ UNAVAILABLE |
How a third asset appears here
As a row, not a redesign. The ledger treats an asset as a configuration record — one declaration in FLASHY_ASSET_DEFINITIONS, validated at load, and every consumer sees it: this page, the discovery endpoint, the balances API. Nothing in the engine knows what gold is, which is exactly why it can settle something else.
Amounts are integers in minor units everywhere in the read API. Decimals is the field that matters — it is the only thing telling a caller how to read them. Flashy Gold is earned and redeemed, not traded.