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.
T20 · Clarification and discussion states retain next action
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | API · E2E |
| Priority | P1 |
| Gates | A02, A07 |
| Build step | Step-06-Questions-Interest-Discussions-Actions |
| Decisions | Q05 |
Given
A requests clarification on B interest; an accepted discussion later has an assigned action.
When
B clarifies; A accepts; permitted user puts the discussion on hold and resumes.
Then / oracle
Clarification preserves EOI/version history. Status changes follow a defined matrix; do not imply partnership execution or erase actions/history. Pending/hold labels agree across participant views. Attributed partnership outcome reporting stays excluded.
Evidence required
Allowed transition tests; chronology; persisted action/assignment; UI state.
Decision dependency (verbatim)
Q05: permitted discussion status transitions and whether hold affects overdue display.
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.