Bid Value Objects¶
Why This Exists¶
This document defines immutable and value-based concepts used by the Bid Domain.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Value objects improve validation, workflow consistency, approval control, submission readiness, and outcome learning.
Value Object Catalogue¶
| Value object | Purpose | Validation rules |
|---|---|---|
| WorkspaceId | Identifies Tender Workspace. | Required, unique, immutable. |
| BidStatus | Workspace lifecycle state. | Controlled values such as planning, drafting, review, approved, submitted, closed. |
| TaskStatus | Bid task state. | To do, in progress, blocked, review, done, cancelled. |
| TaskPriority | Task urgency. | Low, medium, high, critical. |
| ProposalSectionStatus | Section preparation state. | Draft, review, approved, rejected. |
| SBDFormType | Type of standard bidding document. | Controlled values defined by tender context. |
| PricingStatus | Pricing workbook state. | Draft, review, approved, locked. |
| SubmissionReadinessStatus | Submission readiness result. | Not ready, gaps, ready, approved. |
| ApprovalDecision | Approval outcome. | Approved, rejected, changes requested, conditional. |
| SubmissionMethod | Submission method. | Electronic, manual, hybrid, unknown. |
| BidOutcomeResult | Bid result. | Won, lost, cancelled, withdrawn, unknown. |
| LossReasonCategory | Loss feedback category. | Price, compliance, technical, experience, capacity, unknown. |
Submission Rule¶
Submission readiness values must distinguish a draft pack from an approved final pack.
AI Draft Rule¶
AI-generated content status must indicate whether content is suggested, accepted, edited, approved, or rejected.