Contract Database Responsibilities

Why This Exists

This document defines conceptual database responsibilities for the Contract Domain.

It does not define SQL implementation, final schemas, migrations, or storage technology.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Clear persistence responsibilities make contract delivery state auditable, measurable, and available for learning.

Conceptual Tables Or Collections

Conceptual table or collection	Responsibility
contract_workspaces	Root contract workspace state and references.
delivery_plans	Delivery plan metadata and structure.
contract_milestones	Milestone records and status.
contract_deliverables	Deliverable records and status.
supplier_coordination_records	Contract-specific supplier coordination.
contract_variations	Variation records, impact, and approval state.
contract_invoices	Invoice records and status.
contract_payments	Payment records and status.
contract_performance_records	Performance metrics and contract health data.
contract_risks	Risk records and mitigation state.
contract_closeout_records	Closeout checklists and final state.
contract_lessons_learned	Lessons captured from delivery.
contract_audit_log	Contract changes and decision audit.

Indexing Considerations

Future implementation should consider indexes for ContractWorkspaceId, OrganizationId, BidWorkspaceId, award reference, milestone due date, deliverable status, variation status, invoice status, payment status, risk level, closeout status, and correlation ID.

Ownership Rule

Contract storage is canonical for contract delivery state. It must not become the canonical store for bid submissions, supplier master data, funding applications, or intelligence sessions.