Funding Aggregates

Why This Exists

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

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Aggregate boundaries protect funding need, assessment, product, application, recommendation, repayment, and cash-flow risk consistency.

Aggregate Catalogue

Aggregate	Purpose	Boundary
Funding Need	Root aggregate for customer funding need.	Need source, amount, purpose, linked opportunity/bid/contract.
Funding Product Catalogue	Governs funding products and applicability.	Product type, criteria, partner availability.
Funding Partner Profile	Partner relationship context for funding workflows.	Partner status, product support, marketplace display reference.
Funding Application	Application workflow aggregate.	Application status, documents, partner, outcome.
Funding Readiness Assessment	Readiness and eligibility assessment.	Readiness score, gaps, eligibility factors.
Cash-Flow Risk Assessment	Cash-flow risk state.	Risk level, cause, mitigation, linked contract/payment context.
Repayment Tracker	Repayment schedule and status.	Installments, due dates, repayment state.

Aggregate Diagram

flowchart TD
    Need[Funding Need]
    Products[Funding Product Catalogue]
    Partners[Funding Partner Profile]
    Readiness[Funding Readiness Assessment]
    Application[Funding Application]
    Risk[Cash-Flow Risk Assessment]
    Repayment[Repayment Tracker]

    Need --> Readiness
    Products --> Readiness
    Partners --> Application
    Readiness --> Application
    Application --> Repayment
    Need --> Risk
    Repayment --> Risk

Core Invariants

Invariant	Description
Funding need has source context	Need must identify organization and business context.
Application has partner or product	Application must identify funding product or partner.
Recommendations are decision support	Recommendations must not imply final approval or regulated advice.
Cash-flow risk is explicit	Risk requires level, cause, and mitigation where possible.
Funding owns workflow state	Marketplace display and Intelligence reasoning do not own funding workflow state.

Cross-Domain Reference Rule

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