Preventing Double‑Spend: Idempotency, Internal IDs, and the Discipline of State Before Side‑Effects

An idempotent service must never trust client‑supplied names. This piece shows how server‑side identity, atomic state, and UUIDv4 naming prevent double‑spend and keep distributed systems safe under failure.