Suite Store Activate

Bind a paid Agent Mesh entitlement to its holder's agent DIDs and mint the licence.

The mesh settles only for a PARTY to a transaction, so the licence must name its holder. We cannot know that at checkout, hence this step.

Binding is near-permanent by design. Same DIDs => idempotent (re-fetch your licence). Different DIDs => a rebind, allowed only once every REBIND_COOLDOWN (see the constant): rare enough that no one can rebind per-counterparty to run a rail, frequent enough to rescue a lost key. A rebind re-mints the licence bound to the new DIDs under a fresh fulfilment ref and supersedes the old one in our records. The old licence is offline-verifiable, so this cannot claw back a stolen key already in another party's hands — it restores control after a genuine loss.

The read-then-write runs under SELECT … FOR UPDATE. Without that row lock two concurrent activations could both observe "not yet bound" and both mint, quietly defeating the whole control (a TOCTOU race). The lock is load-bearing security, not an optimisation.