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.
DG24 · New service software stays outside Balanced
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Scope guard |
| Layer / kind | Scope guard · design/API review |
| Priority | — |
| Gates | S01, S02, S03, S04, S05, S06, S07 |
| Build step | Step-12-Manual-DG-Services-and-Scope-Guards |
| Decisions | Q12, Q13, Q14, Q15, Q16, Q17, Q18, Q08 |
Given
DG requests joined private thread, proactive named dashboard, automatic ledger/outcomes or refund routing.
When
Review requested change and attempt current ordinary DG routes.
Then / oracle
Record as additional scope, not an existing capability or launch requirement. Current private-body/overdue routes deny. New access model, consent, data, acceptance, costs and schedule require separate decision. Manual procedures do not imply those software features exist.
Evidence required
Change disposition and current access evidence linked T28/T30/T33; future features remain Not included.
Decision dependency (verbatim)
Q08/Q12–Q18 plus D09/D10: explicit scope/acceptance change before development.
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.