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.
T22 · Revision racing with response never silently rebinds
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | API · database · worker |
| Priority | P0 |
| Gates | A05, A08 |
| Build step | Step-04-Opportunities-Versions-Approvals |
| Decisions | Q06 |
Given
B viewed V1; V2 becomes live while B submits, and rule recommendations cached V1.
When
Interleave V2 publication and B submission; consume invalidation and alert jobs twice.
Then / oracle
Recommended rule rejects stale V1 submission for explicit V2 reconfirmation; DG may instead expressly permit immutable V1 response. Never silently bind to V2. Recommendations refresh; duplicate jobs create one logical safe material-revision event. No private response data enters search.
Evidence required
Controlled orderings; immutable references; cache/rule version; duplicate-safe outbox evidence.
Decision dependency (verbatim)
Q06: DG must choose the stale-view oracle; recommended reconfirmation is not approved behavior.
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.