Contract Business Rules¶
Why This Exists¶
This document defines business rules for the Contract Domain.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Rules protect delivery state, variation control, financial tracking, risk management, closeout, and lessons learned.
Rule Catalogue¶
| Rule ID | Area | Rule |
|---|---|---|
| CONT-RULE-001 | Start boundary | Contract starts only after award or contract creation event. |
| CONT-RULE-002 | Bid boundary | Bid owns preparation and submission records. |
| CONT-RULE-003 | Contract ownership | Contract owns delivery state and workflow facts. |
| CONT-RULE-004 | Supplier boundary | Supplier and Marketplace may support delivery but do not own contract state. |
| CONT-RULE-005 | Funding boundary | Funding may support cash flow but does not own contract state. |
| CONT-RULE-006 | Intelligence boundary | AI recommendations require approved Contract actions before state changes. |
| CONT-RULE-007 | Milestones | Milestones must have status and due date or planned sequence. |
| CONT-RULE-008 | Deliverables | Deliverables must link to contract scope or delivery plan. |
| CONT-RULE-009 | Variations | Scope, cost, or schedule changes require variation records. |
| CONT-RULE-010 | Invoices | Invoices must link to contract workspace. |
| CONT-RULE-011 | Payments | Payments must reference invoice or contract financial context. |
| CONT-RULE-012 | Risks | Contract risks must have severity, cause, owner, and status. |
| CONT-RULE-013 | Closeout | Closeout requires delivery, financial, risk, and lesson review. |
Delivery Rule¶
Contract delivery state must be explicit. Informal comments or supplier updates do not replace milestone, deliverable, variation, invoice, payment, risk, or closeout records.