Retiring a Template Version¶
Retiring a template version is the formal act of decommissioning it once it has reached the end of its active lifecycle. It is the final state a template version can occupy within Bizmetry's lifecycle model.
Transition Rule¶
The RETIRED state can only be reached from PUBLISHED:
PUBLISHED → RETIRED
No other transition to RETIRED is permitted. A template version must have been fully validated and published before it can be formally retired.
When the Retire Button is Visible¶
The Retire action is only available when all of the following conditions are met:
| Condition | Requirement |
|---|---|
| Lifecycle state | The version must be in PUBLISHED state. |
| Environment assignment | The version must not be currently assigned to any environment. |
If the version is still assigned to one or more environments, the Retire button is not visible. You must first unassign the version from all environments before retirement becomes available.
What Happens After Retiring¶
Once a template version transitions to RETIRED:
- It cannot be assigned to any environment — including
DEVELOPMENT. - It cannot be referenced from business events, agents, or any other Bizmetry component that relies on an active template version.
- It cannot be edited or transitioned to any other lifecycle state.
- The only remaining action available on a retired version is deletion.
RETIRED is a terminal state
Once a template version is retired, it cannot be reactivated or reused under any circumstance. The transition to RETIRED is irreversible.
However, it is often useful to retain a retired version in the system for historical analysis, audit trails, and post-mortem review. Deletion should only be performed when the version is no longer needed for reference purposes.