Organization Entities¶
Why This Exists¶
This document defines Organization Domain entities with identity.
Entities are business objects whose identity matters over time. They may change attributes while remaining the same entity.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
The Organization Domain owns the entity definitions listed here.
Business Value¶
Clear entity definitions support stable APIs, database responsibilities, domain events, AI reasoning, and cross-domain references.
Entity Catalogue¶
| Entity | Purpose | Key attributes | Business rules | Relationships | MVP status |
|---|---|---|---|---|---|
| Organization | Root customer business entity. | OrganizationId, legal name, trading name, status, registration number, tax identifiers. | Must have stable ID and controlled lifecycle. | Owns or references all Organization aggregates. | MVP |
| Organization User | Person associated with organization usage. | UserId, OrganizationId, role, status, invitation state. | Identity owns credentials; Organization owns association. | Links Organization to Identity. | MVP |
| Director | Legal or governance director. | DirectorId, name, ID/passport reference, appointment status. | Required where compliance or legal profile needs directors. | Belongs to Organization Profile. | MVP |
| Contact | Business contact. | ContactId, name, role, email, phone, contact type. | Contact purpose must be clear. | Used by proposals, contracts, notifications. | MVP |
| Address | Location record. | AddressId, type, address details, geographic coverage, status. | Must validate minimum address details. | Supports branches, compliance, opportunity matching. | MVP |
| Branch | Operating branch. | BranchId, name, address, manager contact, operating status. | Branch belongs to one Organization. | Supports geographic capacity. | Later |
| Department | Internal department. | DepartmentId, name, function, manager, status. | Department names must be unique within organization where active. | Supports enterprise organization structure. | Later |
| Employee | Staff member relevant to procurement capability. | EmployeeId, name, role, skills, employment status. | Sensitive data must be minimized. | Supports capacity and proposal evidence. | Later |
| Service | Service offered. | ServiceId, name, category, description, evidence level. | Service must map to capability or offering category. | Used by matching and proposal content. | MVP |
| Product | Product offered. | ProductId, name, category, description, availability. | Product must have clear offering context. | Used by marketplace and matching. | Later |
| Capability | Organization capability evidence. | CapabilityId, name, classification, evidence level, verification status. | Capability claims require evidence and status. | Supports matching, compliance, proposals. | MVP |
| Equipment | Equipment asset. | EquipmentId, type, description, ownership status, verification status. | Equipment must belong to Organization or be explicitly available. | Supports capability evidence and delivery readiness. | Later |
| Fleet Asset | Vehicle or fleet asset. | FleetAssetId, type, registration, capacity, status. | Fleet asset status must be current for delivery claims. | Supports logistics and contract delivery. | Later |
| Past Project | Completed project. | PastProjectId, client, value range, date range, scope, outcome. | Project evidence should be verifiable where used for claims. | Supports experience and proposals. | MVP |
| Client Reference | Reference contact or record. | ClientReferenceId, client name, contact, project, verification status. | Consent and accuracy must be respected. | Supports trust and proposal evidence. | Later |
| Certification | Certification record. | CertificationId, name, issuer, issue date, expiry date, status. | Expired certifications must not be presented as current. | Supports compliance and eligibility. | MVP |
| Licence | Licence or permit record. | LicenceId, type, issuer, number, expiry date, status. | Expired licences must be flagged. | Supports regulated procurement. | MVP |
Entity Identity Rules¶
- Entity IDs must be stable.
- Entity IDs should be opaque and not encode mutable business meaning.
- Entity lifecycle state must be explicit where relevant.
- Entity updates should publish domain events when other domains need to react.
MVP Status Meaning¶
| Status | Meaning |
|---|---|
| MVP | Required for early Organization Domain value. |
| Later | Important but not required for the first complete foundation. |
| Enterprise | Required for complex enterprise customers and future maturity. |