Contract Relationships

Why This Exists

This document explains how Contract relates to Bid, Organization, Supplier, Marketplace, Funding, Intelligence, Notification, and Analytics.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Clear relationships allow contract delivery to coordinate with supporting domains while preserving Contract ownership of delivery state.

Relationship Diagram

flowchart TD
    Bid[Bid]
    Contract[Contract]
    Organization[Organization]
    Supplier[Supplier]
    Marketplace[Marketplace]
    Funding[Funding]
    Intelligence[Intelligence]
    Notification[Notification]
    Analytics[Analytics]

    Bid --> Contract
    Organization --> Contract
    Supplier --> Contract
    Marketplace --> Contract
    Funding --> Contract
    Intelligence --> Contract
    Contract --> Notification
    Contract --> Analytics

Relationship Map

Domain	Relationship	Ownership boundary
Bid	Provides award or contract creation trigger and submission context.	Bid owns submission records.
Organization	Supplies customer identity, resources, people, services, and capabilities.	Organization owns company facts.
Supplier	Supports supplier coordination.	Supplier owns supplier master records.
Marketplace	Supports supplier sourcing or marketplace coordination.	Marketplace owns marketplace records.
Funding	Supports cash flow, invoice funding, or payment support.	Funding owns funding state.
Intelligence	Monitors, summarizes, and recommends.	Intelligence owns reasoning sessions, not contract state.
Notification	Sends milestone, risk, invoice, payment, and closeout alerts.	Notification owns delivery records.
Analytics	Consumes contract events and performance data.	Analytics owns projections.

Ownership Rule

Contract owns contract workflow state. Supporting domains may contribute information or actions, but contract delivery facts remain Contract-owned.