THE REPRESENTATION RULENever count the same claim twice.
At inception, Participant A holds 750 units and Participant B holds 250 in the traditional ledger. No token exists. When 180 units are reserved for token issuance, they leave the free legacy balance and enter escrow; an in-flight claim of 180 remains visible until issuance is completed or cancelled. Once the token is issued, that in-flight claim is replaced by the token claim, and the reserve continues to back it. The same underlying value therefore cannot simultaneously appear as a free legacy claim and as a token claim.
Economic claim conservation: free legacy claims + available token claims + in-flight claims = the initial 1,000 units. Escrow is explicitly excluded from this sum because it is backing, not another spendable claim.
THE COVERAGE RULEReserve must match representation.
The reference model enforces a one-to-one relationship between encumbered reserves and outstanding represented claims: escrow = available token claims + pending issue, transfer and redemption claims. Issuance moves a claim from a pending slot into the token ledger; a token-to-token transfer temporarily holds a claim in transit; redemption converts a pending claim into free legacy balance and releases an equal reserve amount.
Coverage difference: escrow − (available token claims + in-flight claims) = zero. Positive and negative differences are both flagged because this simplified model requires equality rather than general overcollateralisation.
THE TWO-SIDED GATEPrepared is not final.
Issuance and redemption require separate legacy and token acknowledgements before they may be committed. A token-only transfer requires a token acknowledgement; its backing remains in legacy escrow. Duplicate commit requests for an already completed operation are ignored using the operation identifier. If transport is partitioned, no new acknowledgements or commit are allowed. These choices are deliberately conservative model rules, not a specification of any production protocol.
Three or more model intervals without finalisation produce an ageing warning. The model does not interpret synthetic intervals as real-world seconds, nor does it infer a legal settlement event from a successful simulated commit.
THE FAILURE BOUNDARYA defect must be demonstrable.
Two intentionally invalid adapters expose specific failures: a duplicate token issue and a premature reserve release. They bypass normal protocol gates and therefore generate a reproducible conservation or coverage violation. The model responds with an integrity interlock that prevents ordinary follow-on actions until reset. An interlock is only a local teaching mechanism; it is not a live recovery, bank resolution or incident response procedure.
Exported records include parameters, ledger balances, events and identified invariant breaches. Replaying the same scenario with the same integer amount produces the same ledger events, excluding the export timestamp.