A Lifecycle State identifies the condition of a modeled thing at a specified time during its existence.
A Lifecycle State provides a stable semantic representation of the modeled thing between applicable transitions. A change from one Lifecycle State to another may be caused, authorized, observed, or recorded by a Lifecycle Event.
A Lifecycle State may identify:
A Lifecycle State is distinct from a Lifecycle Stage. A Lifecycle Stage represents a broader phase of a lifecycle and may contain multiple Lifecycle States.
A Lifecycle State is also distinct from a Lifecycle Event. A Lifecycle State represents a condition that applies at a specified time or during a specified period. A Lifecycle Event represents an occurrence that may cause, authorize, observe, or record a transition between states.
A Lifecycle State may be specialized for a particular kind of modeled thing. Examples include:
condition of a modeled thing at a specified time during its existence
Adapted from:
This definesLifecycle State as the general concept specialized by Operational Lifecycle State, Logical Node Lifecycle State, Agreement Lifecycle State, and other domain-specific lifecycle-state concepts.
An Agreement progresses through Proposed, Under Negotiation, Executed, Effective, and Expired Lifecycle States.
The execution of the Agreement is a Lifecycle Event that causes or records a transition from Under Negotiation to Executed.
The arrival of the Effective Date causes or records a transition from Executed to Effective.
The current Lifecycle State does not overwrite the earlier state assignments. Each state and transition remains available in the Agreement's lifecycle history.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.