Process Lifecycle¶

Executive Summary¶

The Process Lifecycle defines how Business Processes move from draft design to operational use, measurement, optimization, automation, and retirement. It applies to all future Algosure process definitions.

Why This Exists¶

Processes are living operating assets. They must be introduced carefully, governed during use, improved with evidence, and retired when no longer fit for purpose. A lifecycle prevents unmanaged process drift.

Owner¶

The owner is the Chief Product Officer and Enterprise Architect. Each process lifecycle is managed by the owning Practice with governance support from the Executive Office and AIOS.

Business Value¶

A defined lifecycle improves operational discipline, audit readiness, automation readiness, change control, and continuous improvement.

Lifecycle States¶

stateDiagram-v2
    [*] --> Draft
    Draft --> Reviewed
    Reviewed --> Approved
    Approved --> Pilot
    Pilot --> Operational
    Operational --> Optimized
    Optimized --> Automated
    Automated --> Retired
    Operational --> Deprecated
    Deprecated --> Retired
    Draft --> Retired

State	Meaning	Required Control
Draft	Process is being designed.	Owner, scope, and outcome must be defined.
Reviewed	Process has been reviewed by relevant Practices and Domains.	Ownership and Domain boundaries validated.
Approved	Process is authorized for pilot or operational use.	Approval record required.
Pilot	Process is tested in controlled operating conditions.	Exceptions and KPI baselines captured.
Operational	Process is approved for normal use.	KPIs, audit, and governance cadence active.
Optimized	Process has evidence-based improvements.	Improvement rationale and version history recorded.
Automated	Approved steps are orchestrated or executed through AIOS.	Automation level and approval gates documented.
Deprecated	Process should no longer be used for new work.	Replacement or retirement plan required.
Retired	Process is no longer active.	Historical audit and version records retained.

Transition Rules¶

Draft cannot become Operational without review and approval.
Pilot must capture exceptions and KPI evidence.
Automation requires defined guardrails and approval gates.
Deprecated processes must identify replacement guidance.
Retired processes must remain available for historical audit where required.

Process Change Events¶

Event	Trigger
ProcessDrafted	A new process is created.
ProcessReviewed	Relevant owners complete review.
ProcessApproved	Process is approved for use.
ProcessPiloted	Controlled execution starts.
ProcessOperationalized	Process becomes active for normal work.
ProcessOptimized	Evidence-based improvement is accepted.
ProcessAutomationLevelChanged	Automation level changes.
ProcessDeprecated	Process is marked for replacement.
ProcessRetired	Process is removed from active use.