Organization Lifecycle¶
Why This Exists¶
This document defines the lifecycle states and transitions for an Organization.
The Organization lifecycle governs when an organization can participate in compliance, opportunities, proposals, contracts, suppliers, funding, learning, analytics, and AI memory.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
The Organization Domain owns lifecycle state and transition rules.
Business Value¶
Lifecycle clarity protects customer trust, prevents invalid workflow participation, and provides downstream domains with reliable business state.
Lifecycle States¶
| State | Meaning | Key rules |
|---|---|---|
| Draft | Organization record is being prepared but not registered. | Not referenceable by downstream active workflows. |
| Registered | Organization has a stable ID and basic identity. | May begin profile completion. |
| Profile Incomplete | Required profile sections are missing. | Limited participation; matching and proposals may be restricted. |
| Active | Organization meets activation criteria. | Eligible for full Algosure participation. |
| Suspended | Organization is temporarily restricted. | Active workflows may pause or require review. |
| Archived | Organization is no longer active but retained. | Read-only history and memory retention rules apply. |
| Deleted/Retained | Organization is deleted where allowed or retained for legal/audit reasons. | Access and retention governed by policy. |
State Diagram¶
stateDiagram-v2
[*] --> Draft
Draft --> Registered: OrganizationRegistered
Registered --> ProfileIncomplete: OrganizationProfileCreated
ProfileIncomplete --> Active: OrganizationActivated
Registered --> Active: OrganizationActivated
Active --> Suspended: OrganizationSuspended
Suspended --> Active: OrganizationActivated
Active --> Archived: OrganizationArchived
Suspended --> Archived: OrganizationArchived
Archived --> DeletedRetained: RetentionDecisionApplied
DeletedRetained --> [*]
Transitions¶
| Transition | Required event | Business rules |
|---|---|---|
| Draft to Registered | OrganizationRegistered | ORG-RULE-001, ORG-RULE-002 |
| Registered to Profile Incomplete | OrganizationProfileCreated | ORG-RULE-005 |
| Profile Incomplete to Active | OrganizationActivated | ORG-RULE-003 |
| Registered to Active | OrganizationActivated | ORG-RULE-003 |
| Active to Suspended | OrganizationSuspended | ORG-RULE-004 |
| Suspended to Active | OrganizationActivated | Governance review required. |
| Active to Archived | OrganizationArchived | ORG-RULE-016, ORG-RULE-017 |
| Archived to Deleted/Retained | RetentionDecisionApplied | Retention and audit policy required. |
State Rules¶
Draft¶
Draft records are not authoritative. They may be used for onboarding workflows but should not be treated as customer business context for procurement execution.
Registered¶
Registered organizations have stable identity. Downstream domains may reference the OrganizationId but must respect activation and completeness state.
Profile Incomplete¶
Profile Incomplete organizations require action before full procurement use. AI may suggest missing information, but customer review is required.
Active¶
Active organizations may participate in opportunity matching, proposals, compliance checks, supplier workflows, funding workflows, learning, and analytics.
Suspended¶
Suspended organizations are restricted. Suspension should preserve data and memory while preventing inappropriate activity.
Archived¶
Archived organizations are no longer active. Historical records may remain available for audit, analytics, and retention.
Deleted/Retained¶
Deletion or retention must respect legal, audit, customer, and platform requirements.