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.
DG17 · Duplicate requests do not inflate work or charges
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Manual DG service |
| Layer / kind | Manual · duplicate rehearsal |
| Priority | — |
| Gates | S07 |
| Build step | Step-12-Manual-DG-Services-and-Scope-Guards |
| Decisions | Q12, Q16, Q17 |
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.