Versioned quotations, separate requester and approver roles, currency rules and transactional audit records. A business-analysis case study built around the question: which version was actually approved?
- Status
- Local case study
- AI in the product
- None: a business-rules study
- Evidence
- Local PostgreSQL tests; backup and restore check
- Limits
- Simulated data and roles
Decisions worth testing
Reject approvals against stale quotation versions, prevent self-approval, use decimal arithmetic for money, and roll back a write if its audit record fails.
Evidence and limits
The repository records local PostgreSQL tests and a backup/restore check. Data and roles are simulated; production identity, monitoring and deployment are outside the demonstrated scope.