Custom and built-in access definition

The Lifecycle

The diagram summarizes the observed transition rows; declared edges without an observed writer remain outside the operational graph.

Transitions Explained

Custom and built-in definitions share active and archived states but have different writers. Custom administration supports archive, while release reconciliation can restore a built-in identity.

Custom version checks are optional in the current routes. Built-in content equality avoids unnecessary version changes; it does not prove that every surrounding deployment action is a no-op.

What Cannot Happen

Customers cannot unarchive definitions through an administration route; they can create or copy a replacement.

Archive is refused for built-ins outside reconciliation and for custom definitions that remain assigned or composed.

Concurrency and Timing

Supplied custom-definition versions are checked, but omission is currently accepted and remains debt against the record-write contract. Database safeguards limit built-in writes to reconciliation context. Catalog reconciliation uses a database transaction; registry activation in a separate store is outside that transaction.