CA-UNILIF · Unit Lifecycle
The lifecycle stages available to units of each configured type.
Configuration artifact
CA-UNILIF configures the lifecycle stages a unit of each type can move through. An organization can author it explicitly where staged progression matters, or omit it and let an implicit single-stage default stand in its place.
How It Works
When authored, CA-UNILIF configures the lifecycle stages per unit type, and so it requires CA-UNITYP first. When it is omitted, the effective lifecycle basis collapses to one default stage — and that implicit single-stage basis is treated as the effective validated CA-UNILIF state for the artifacts that depend on it. Either way, downstream behavior always has an effective lifecycle basis to read against.
Dependency role. CA-UNILIF is optional explicit authoring. Its prerequisite is CA-UNITYP validated. Validated explicitly, or present implicitly as the single-stage default, it provides the effective lifecycle basis that unlocks CA-PLMGMT and contributes to unlocking CA-GTMACC.
Statements
- CA-UNILIF means Unit Lifecycle.
- CA-UNILIF configures lifecycle stages per unit type.
- CA-UNILIF requires CA-UNITYP validated.
- CA-UNILIF can be explicitly authored.
- CA-UNILIF can also be represented by an implicit single-stage default.
- The implicit single-stage default counts as the effective validated lifecycle basis for CA-PLMGMT and CA-GTMACC.
Why It Matters
Financial governance and go-to-market access are lifecycle-sensitive: they read against the stage a unit is in. CA-UNILIF supplies that lifecycle basis. Making it optional keeps simple organizations simple, while the single-stage default guarantees the lifecycle axis never disappears from downstream logic.
Related
- CA-UNITYP — the prerequisite of CA-UNILIF.
- CA-PLMGMT — what the effective lifecycle basis unlocks.
- Dependencies — the CA-UNILIF shortcut explained in the graph.