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.

DG17 · Duplicate requests do not inflate work or charges

FieldValue
StatusNot executed
TypeManual DG service
Layer / kindManual · duplicate rehearsal
Priority—
GatesS07
Build step06 (GGA order; the 1.3 step is history)
DecisionsQ12, Q16, Q17

Disposition under GGA

FieldValue
DispositionReframed
GGA basisBlueprint pp. 14, 15 (GGA-Requirement-Register)
Replaced or carried byGS12-staged, GS23-staged
Still opennone
What changesDuplicate requests do not create a second grant, invoice or term; idempotency keys scope to actor and action.

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 repeats a request; one joint session serves separately disclosed duties to A and B.

When

Resolve duplicate against existing case/activity; prepare separate company receipts.

Then / oracle

One real activity recorded once; repeat gets existing reference and no automatic second activity/charge/disclosure. Each receipt describes only own contracted benefit, no double independent-introduction claim. Each commercial obligation remains distinct; no charge amount is decided.

Evidence required

One internal activity with separate redacted client references; duplicate handling and linked obligations.

Decision dependency (verbatim)

Q12/Q16/Q17: billing/remedy terms and authorised ledger; no payment engine.

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.