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.
T21 · Material revision preserves V1 while V2 is reviewed
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | API · database · E2E |
| Priority | P0 |
| Gates | A05 |
| Build step | Step-04-Opportunities-Versions-Approvals |
| Decisions | Q06 |
Given
V1 is live with B EOI referencing V1; A edits a typo or offers/needs/geography/terms/disclosure in V2.
When
Save V2, review, return, then approve/publish V2.
Then / oracle
All published edits are versioned and published by an entitled approver; typo classification is not contributor bypass. V1 stays live while V2 is reviewed unless separately paused. B/C see V2 only after approved publication; old EOI still references V1. Material changes trigger agreed alert; typo does not under recommended classification.
Evidence required
Version hashes; live pointer after each step; unchanged historical EOI FK.
Decision dependency (verbatim)
Q06: DG material-field/rubric and stale-view policy. Typo classification is proposed; every new revision still requires exact-version publication authority.
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.