Capability binding lifecycle

The Lifecycle

Transitions Explained

A new eligible choice becomes current. Replacement or removal retires the old row while advancing scope history. Dependency changes can make the current row invalid and later restore it, without removing the administrator’s selection.

What Cannot Happen

History rows cannot become current again; a new row continues the scope revision. Initial put validation refuses an ineligible account choice.

Concurrency and Timing

The write path serializes current choices and protects applicable uniqueness. Reassessment shares the dependency-change transaction, and rollback discards notices. A current invalid binding still blocks disconnection, so the removed draft edge cannot occur through ordinary closure.