Contract Aggregates

Why This Exists

This document defines aggregate boundaries for the Contract Domain using Domain-Driven Design.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Aggregate boundaries protect delivery state, milestones, deliverables, variations, invoices, payments, performance, risks, closeout, and learning.

Aggregate Catalogue

Aggregate	Purpose	Boundary
Contract Workspace	Root aggregate for contract delivery.	Contract status, award reference, delivery plan, key artefact references.
Delivery Plan	Plan for milestones, deliverables, responsibilities, and dates.	Milestone and deliverable planning state.
Variation Register	Governs contract variations.	Variation requests, approvals, impact, status.
Financial Tracking	Tracks invoices and payments.	Invoice state, payment state, cash flow references.
Performance Register	Tracks performance indicators and contract health.	Performance records and health state.
Risk Register	Tracks contract risks and mitigations.	Risk state, severity, owner, mitigation.
Closeout Record	Governs closure and lessons learned.	Completion, final checks, lessons, closeout status.

Aggregate Diagram

flowchart TD
    Workspace[Contract Workspace]
    Plan[Delivery Plan]
    Variations[Variation Register]
    Finance[Financial Tracking]
    Performance[Performance Register]
    Risks[Risk Register]
    Closeout[Closeout Record]
    Bid[Bid Award Reference]

    Bid --> Workspace
    Workspace --> Plan
    Workspace --> Variations
    Workspace --> Finance
    Workspace --> Performance
    Workspace --> Risks
    Workspace --> Closeout

Core Invariants

Invariant	Description
Contract starts after award	Contract workspace requires award or contract creation event.
Contract owns delivery state	Delivery workflow state is canonical in Contract.
Variations are explicit	Scope, cost, or schedule changes require variation records.
Closeout requires review	Contract closeout requires milestone, deliverable, financial, and risk review.
AI suggestions are not facts	Intelligence suggestions require approved Contract actions.

Cross-Domain Reference Rule

Contract references Bid, Organization, Supplier, Funding, and Intelligence records by ID. It does not own their source facts.