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.

DG01 · Each payer knows what its own service buys

FieldValue
StatusNot executed
TypeManual DG service
Layer / kindManual · agreement review
Priority—
GatesS01
Build step12 (GGA order; the 1.3 step is history)
DecisionsQ12

Disposition under GGA

FieldValue
DispositionSuperseded
GGA basisBlueprint pp. 1, 8 (GGA-Requirement-Register)
Replaced or carried byGS22-staged
Still opennone
What changesThere is no per-client service catalogue or per-service charge. What carries over: the payer sees amount, tax treatment, period basis and terms version before consent.

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

Synthetic A and B are considering separate paid DG services; fee amounts and commercial rules are unset.

When

Review each proposed service description before payment or service acceptance.

Then / oracle

Each identifies deliverable, exclusions, completion evidence, unmet condition, owner, review window and complaint/remedy route. Software delivery to DG is separate. No invented price, guaranteed response/deal or after-the-fact replacement of an introduction by search work.

Evidence required

Separate A/B agreement templates and acceptance checklist; blank price/windows; no actual charge claimed.

Decision dependency (verbatim)

Q12: DG service catalogue, per-client obligations and terms before selling; D09 remains open.

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.