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.
T40 · Restore, migration and release evidence are controlled
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | Database · operations · UAT |
| Priority | P0 |
| Gates | A08, A10 |
| Build step | Step-10-Hardening-and-Operations |
| Decisions | Q09, Q11 |
Given
Backup includes memberships, versions, EOI references, outbox and audit; emails target an isolated sink. A migration and rollback/forward-recovery plan exist.
When
Restore into isolated staging; verify invariants and recover interrupted work; rehearse migration and release checks.
Then / oracle
Data/references and access policy restore correctly; jobs do not replay delivery blindly. Measure data-loss/recovery windows against approved targets. No launch without DG UAT sign-off and separate written go-live approval; repository/runbooks/owners are handed over.
Evidence required
Restore/migration report; known record counts/hashes; mail-sink receipts; UAT evidence and release checklist.
Decision dependency (verbatim)
Q09/Q11: recovery/retention objectives, migrations, UAT/launch owners and defect acceptance.
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.