Name Lifecycle Transitions
BOUNDARY-NAME-LIFECYCLE-TRANSITIONS
Summary
Model creation, activation, cancellation, teardown, reload, and promotion as named operations when they carry different invariants. This keeps ordering, cleanup, retry, and recovery rules visible without adding ceremony to simple constructed values.
Rule
Treat lifecycle transitions as named operations.
Why
Creation, activation, cancellation, teardown, reload, and promotion are different operations with different invariants. Treating them as incidental flag changes makes cleanup, retries, and error recovery harder to reason about.
Helps
- Makes lifecycle behavior explicit and keeps invalid ordering visible.
Limits
Do not invent lifecycle ceremony for values that are simply constructed and dropped. Name transitions when resources, external effects, or stateful protocols are involved.
Agent Instruction
Treat lifecycle transitions as named operations because creation, activation, cancellation, teardown,
reload, and promotion are different operations with different invariants.Mechanisms
Supported by transition methods, state enums, RAII guards, cancellation tokens, teardown tests, and docs for caller obligations.