Configuration record availability

The Lifecycle

Transitions Explained

Programs, types, reasons and policy sets default to active but can be created inactive. Saving activity changes availability without removing existing references. A used record is retained through retirement, and deletion removes only an unreferenced record.

What Cannot Happen

Protected dependencies prevent deletion. Reusing a deleted readable identifier is a fresh creation. The stored lock flag does not block these operations, and activity does not have one uniform consumer rule.

Concurrency and Timing

Updates and deletions check the version read. Live consumers see new settings on their next read; this does not imply every consumer checks retirement, and stored policy sets remain unused.