Compliance Value Objects¶

Why This Exists¶

This document defines immutable and value-based concepts used by the Compliance Domain.

Value objects make validation, scoring, status, and expiry semantics explicit.

The owner is the Chief Product Officer and Enterprise Architect.

Precise value objects improve readiness scoring, risk calculation, verification quality, and AI explainability.

Value object	Purpose	Validation rules
ComplianceProfileId	Identifies compliance profile.	Required, unique, immutable.
ComplianceRequirementId	Identifies requirement.	Required, unique, immutable.
ComplianceDocumentType	Classifies document.	Controlled values such as SARS, CIPC, CSD, CIDB, COIDA, B-BBEE, licence, certificate.
ComplianceStatus	Current compliance state.	Controlled values such as incomplete, ready, at risk, non-compliant.
VerificationStatus	Verification state.	Controlled values such as unverified, pending, verified, rejected, expired.
ExpiryDate	Date evidence expires.	Must support non-expiring and unknown cases explicitly.
RenewalWindow	Period before expiry requiring action.	Must be positive and policy-controlled.
ProcurementReadinessScore	Readiness score.	Numeric range with component breakdown and date.
ComplianceRiskLevel	Risk severity.	Controlled values low, medium, high, critical.
EvidenceStrength	Strength of evidence.	Controlled values claimed, uploaded, reviewed, verified.
ComplianceSource	Source of requirement or evidence.	SARS, CIPC, CSD, CIDB, COIDA, B-BBEE, tender, internal policy, other.
RequirementApplicability	Whether requirement applies.	Applicable, not applicable, conditional, unknown.
AISuggestionConfidence	Confidence for AI suggestion.	Numeric range, model/source, timestamp required.

Expiry-related value objects must distinguish:

AI confidence is not verification. Compliance must decide whether suggestions become compliance facts.