Release-controlled shared definitions

Context

The cited release reconciliation decision is retained. Its database transaction does not include activation of the route registry in another store.

The corrected workflow records the publication gap and intended replay recovery; content idempotence is narrower than a write-free deployment.

Decision

Reconcile declared permissions, tier policies and built-in definitions transactionally in the catalog, increasing a built-in version only when its materialized content changes.

Alternatives Considered

Rewrite every built-in on every deployment. Unchanged deployments would move versions without a permission change and weaken explanations of what a version means.

Allow customers to edit shared built-ins. A shared definition affects multiple customers; local customization must use a customer-owned copy.

Consequences

Unchanged built-in content preserves its version; catalog publication can still perform other writes.

Removed built-ins are archived with impact history and can return under the same identity.

Customer customization creates a copy rather than modifying shared content.