Organization Business Rules¶
Why This Exists¶
This document defines business rules for the Organization Domain.
Business rules protect domain integrity and keep Organization as the authoritative source of customer business context.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
The Organization Domain owns the rules listed here.
Business Value¶
Business rules improve trust, data quality, compliance readiness, AI reasoning quality, and cross-domain consistency.
Rule Catalogue¶
| Rule ID | Area | Rule |
|---|---|---|
| ORG-RULE-001 | Registration | An Organization must have a stable OrganizationId before any downstream domain may reference it. |
| ORG-RULE-002 | Registration | Legal name or trading name must be present before registration can be completed. |
| ORG-RULE-003 | Activation | Organization activation requires minimum profile completeness. |
| ORG-RULE-004 | Activation | Suspended or archived organizations cannot be activated without governance review. |
| ORG-RULE-005 | Profile completeness | Profile completeness must consider identity, contact, address, offerings, and evidence requirements. |
| ORG-RULE-006 | Ownership | Each Organization must have one primary accountable owner. |
| ORG-RULE-007 | Users | Organization users must be linked through Identity but governed by Organization association. |
| ORG-RULE-008 | Directors | Director records used for compliance must include verification status. |
| ORG-RULE-009 | Capabilities | Capability claims must distinguish claimed, documented, and verified evidence. |
| ORG-RULE-010 | Services | A service must have a business-readable name and category before being used for opportunity matching. |
| ORG-RULE-011 | Products | A product must have a business-readable name and availability status before marketplace use. |
| ORG-RULE-012 | Equipment | Equipment claims must identify ownership or availability basis. |
| ORG-RULE-013 | Experience | Past projects used in proposals must include scope and date range. |
| ORG-RULE-014 | Procurement preferences | Preferences must be customer-owned and editable. |
| ORG-RULE-015 | AI-enriched information | AI-suggested facts must carry source, confidence, timestamp, and review status. |
| ORG-RULE-016 | Archiving | Archived Organizations must not participate in active procurement workflows. |
| ORG-RULE-017 | Archiving | Archived data must follow retention and audit requirements. |
| ORG-RULE-018 | Cross-domain ownership | Other domains may reference Organization data but must not overwrite canonical Organization state. |
Registration Rules¶
Registration establishes the root aggregate. It must create a stable OrganizationId and initial lifecycle state.
Activation Rules¶
Activation indicates the organization can participate in broader Algosure workflows. Activation should not be treated as automatic registration.
AI-Enriched Information Rules¶
AI may suggest organization classifications, capability evidence, profile gaps, and preference recommendations. AI-enriched information must be marked and reviewable before it becomes trusted Organization data.
Business Rule Review¶
Rules should be reviewed when Organization lifecycle, capabilities, policies, APIs, events, or database responsibilities change.