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.
Step 11 · UAT and release
Goal. DG acceptance testing and separately authorised launch; the point where integrated evidence is rechecked.
Not started. This is a specification; no code has been written. The primary-step mapping is an index, not proof that each full scenario can be completed in its step: see Dependency-and-Regression-Table.
Prerequisites
Step 10. Blocked until DG decides: named reviewer, launch approver, defect criteria and review window (Q11).
Changes (illustrative, not a final schema)
No new feature work; acceptance evidence assembly and release procedure.
Build items:
- Acceptance annex scoped to Balanced; evidence per scenario
- UAT with contributor, approver, viewer and DG accounts
- Defect criteria; zero unresolved critical/high security defects
- Written launch approval; smoke check; monitored rollout
Expected outputs and invariants
Integrated evidence for every scenario variant; written launch approval before any launch.
Tests-first subset
Primary scenarios of this step (write these tests first): none have this step as their primary step.
Assertions to write first: Recheck, on the integrated build, of every software scenario in the Dependency-and-Regression-Table that depends on later components.
Method: make one meaningful test fail for the expected reason, implement the minimum behaviour, refactor without changing the observable contract. A scenario whose decision is still pending stays Pending decision; no oracle is invented.
Deferred integration checks
Scenarios whose primary step is this one but whose full variants need later components:
- None: the scenarios of this step can be completed here.
Follow-up verification brought here
Earlier scenarios that can only be completed or rechecked once this step exists:
- T37 — Needs actual identity, role and revocation behaviour (02, 03), protected DG admin operations with MFA (09) and an integrated recheck (11).
- T40 — Release evidence is to be verified in step 11.
Decisions DG must settle (dependent behaviour stays blocked until DG chooses)
Exit evidence
No software scenario is recorded as Passed until all of its relevant variants have been exercised on a named integrated build. DG signs the acceptance annex; written launch approval exists. Software UAT and acceptance are limited to the agreed Balanced annex: manual-service rehearsals (step 12) need no application build and are not a software payment gate.
Evidence is recorded only for a named build and fixture. A software scenario is not recorded as Passed until all its relevant variants have been exercised on a named integrated build (step 11).
Navigation: Step-10-Hardening-and-Operations ← this step → Step-12-Manual-DG-Services-and-Scope-Guards · Implementation-Order-Overview
A11 coverage disposition
Use A11-Language-and-Email-Checklist after applicable D07/Q07/Q11 confirmation. Japanese translation remains excluded, never passed; English UI and the agreed safe email templates have only proposed, Not executed checklist coverage.