Settlement coordinators should partition canonical support without becoming stock ledgers

For replay-safe exchange or workflow settlement, derive a canonical physical support key before any adapter or envelope identity, then enforce one global claim partition across every consumer. Default reusable multiplicity to one; values above one require an explicit finite, rename-invariant response coordinate or exact use slots with their production, copy, or interface costs accounted. Keep the settlement balance as a projection over exact authoritative stock slices and committed disposition events, never as a second mutable account. Earning should create only a disposition instruction: remote availability begins after ordinary custody handoff, dispatch, transit, loss, and arrival. Rebinding may create a descendant envelope but must retain one immutable lifecycle and empirical root so replay, outside-value, and evidence deduplication cannot reset.