Lifecycle Participant

What It Models

A participant declares one application area’s construction, reset, removal and export responsibilities. Platform orchestrates those declarations while applications retain their implementations.

Identity and Attributes

The participant uses its stable service-prefixed key; seed and resource identities additionally include workspace scope. A stable service-prefixed participant identity. The application responsible for invoking this participant; Platform participants execute locally. Construction predecessors and reverse removal dependencies, with Platform’s workspace row added for remote participants. Platform’s integration switch; disabled declarations can be returned when other participants of that service are enabled. Declared tables, provider resources and storage prefixes, with removal and export treatment. Versioned starter groups; the ledger is the intended application-once mechanism. Declared construction, readiness, removal, inventory, reset, initialization or dataset-export support. Per-workspace seed, set version and applying-run evidence in the applications that implement a ledger. Scoped external-resource key, recorded state, creation facts and optional removal time. Named export datasets and treatment of resources excluded from delivery.

Relationships

The construction plan invokes participant work. Reset classification chooses participant removal while preserving retained concerns. The deletion plan invokes removal and inventory.

Invariants

The structured invariants distinguish service and database enforcement from documented obligations. The participant completeness and seed requirements describe the intended contract; known omissions prevent a universal guarantee.

How It Is Stored and Shared

Platform’s lifecycle service owns this design object. Applications own participant implementations and their local ledgers; Platform retains orchestration declarations and its resource register.

Open Design Questions

Static manifest drift, Commerce’s missing ledger and Websites’ incomplete accounting limit the declared contract. Resource states have no successor guard, and some registration and cross-application policy evidence remains outside this review.