Registered declaration lifecycle

The Lifecycle

Transitions Explained

Deployments replace complete declaration sets. Included declarations become live; omissions become retained retirement. Later redeclaration restores access to the retained configuration.

What Cannot Happen

Owner registration can retire or revive a retained declaration but cannot erase it through a workspace action.

Concurrency and Timing

One invocation changes one application’s registry transactionally. The two-invocation limit does not serialize complete same-application manifests; row locking alone leaves concurrent-release retirement unresolved. Search degradation occurs in later workspace transactions.