Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
T33 · Business state and notification event commit together
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | Database · worker · failure injection |
| Priority | P0 |
| Gates | A08 |
| Build step | Step-07-Outbox-Worker-Email |
| Decisions | Q07 |
Given
Each allowed event is parameterized: new interest, assigned question, accepted discussion, material revision.
When
Fail before transaction commit, just after commit and before job acknowledgement; retry the business request.
Then / oracle
Business state and corresponding outbox commit together or neither does. Post-commit failure remains recoverable. Retry does not create duplicate business/event identity. Rejected requests never produce a sendable event.
Evidence required
Transaction snapshots; one logical event per change; durable outbox state after restart.
Decision dependency (verbatim)
Q07: event trigger and current responsible-recipient matrix; no unapproved message/overdue events.
Source: TDD rev 1.3 (PDF); machine-readable in 10-Sources/tdd-bundle/. Back to Scenario-Index · Traceability-Matrix · integration dependencies in Dependency-and-Regression-Table.