Compliance Lifecycle

Why This Exists

This document defines the lifecycle of compliance state, documents, evidence, readiness, and risk.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Lifecycle clarity allows Algosure to monitor readiness, prevent expired evidence from being used, and explain compliance risk.

Compliance Profile Lifecycle

State	Meaning
Not Created	No compliance profile exists for Organization.
Created	Compliance profile exists.
Incomplete	Required evidence or profile sections are missing.
Ready	General procurement readiness threshold is met.
At Risk	Missing, expired, or weak evidence creates risk.
Suspended	Compliance participation is restricted.
Archived	Compliance profile is retained for history.

State Diagram

stateDiagram-v2
    [*] --> NotCreated
    NotCreated --> Created: ComplianceProfileCreated
    Created --> Incomplete
    Incomplete --> Ready: ReadinessThresholdMet
    Ready --> AtRisk: ComplianceRiskIdentified
    AtRisk --> Ready: ComplianceRiskResolved
    Ready --> Suspended: ComplianceSuspended
    AtRisk --> Suspended: ComplianceSuspended
    Suspended --> Ready: ComplianceReinstated
    Ready --> Archived: ComplianceArchived
    Suspended --> Archived: ComplianceArchived
    Archived --> [*]

Document Lifecycle

State	Meaning
Uploaded	Document has been uploaded or registered.
Pending Review	Document requires review or verification.
Verified	Document has been verified.
Rejected	Document was rejected.
Expiring	Document is inside renewal window.
Expired	Document expiry date has passed.
Archived	Document retained for history.

Required Events

Lifecycle transitions should publish events such as ComplianceDocumentUploaded, ComplianceEvidenceVerified, ComplianceDocumentExpired, ProcurementReadinessScoreUpdated, and ComplianceRiskIdentified.

Lifecycle Rule

Tender-specific compliance must be assessed separately from general readiness.