Status. Proposed design only. Nothing in this vault is GGA client approval. The GGA client documents are supplied drafts: see GGA-Source-Digest. No application, service or test has been executed; every scenario is Not executed. Delivery 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	09 (GGA order; the 1.3 step is history)
Decisions	Q05

Disposition under GGA

Field	Value
Disposition	Reframed
GGA basis	Blueprint p. 6 (GGA-Requirement-Register)
Replaced or carried by	GS24-staged
Still open	GQ04-staged
What changes	Clarification and hold states have no GGA feedback and stay a Proposed carry-forward. The Blueprint follow-through states (introduced, discussion held, pilot, deal, no fit, no response) are in GS24.

The 1.3 text below is kept verbatim as history. Where the disposition is Reframed, Superseded or Parked it is not the GGA oracle; use the replacing scenario. A Parked scenario has no GGA feedback and stays a Proposed carry-forward. The status stays Not executed. Register: Scenario-Dispositions.

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.