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.
DG01 · Each payer knows what its own service buys
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Manual DG service |
| Layer / kind | Manual · agreement review |
| Priority | — |
| Gates | S01 |
| Build step | Step-12-Manual-DG-Services-and-Scope-Guards |
| Decisions | Q12 |
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.