Responsibility holding lifecycle

The Lifecycle

Transitions Explained

Effective dates project scheduled and lapsed standing over stored active rows. Ordinary ending preserves history, while derived and default changes have their own writers. Workspace purge and foreign-key deletion are exceptions to retention.

What Cannot Happen

Ended holdings remain history; new accountability needs a new holding. A removed default is not restored by reconciliation. Removal is reserved for role defaults rather than direct or derived holdings.

Concurrency and Timing

Ending and removal lock the row and require its read version. The direct uniqueness index compares exact validity endpoints and does not prohibit all overlaps. Derived synchronization serializes a derivation key.