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.
Step 11 · Acceptance and release gate
Goal. Run A1 to A12 (GA01 to GA12) on one named integrated build and decide readiness to invite the first 20 companies.
Blueprint delivery stage: Gate before Stage 4 (Delivery-Options-Comparison).
Former 1.3 name: UAT and release. The file name and the step number are kept as stable identifiers (as with the historical DG prefix), so existing links and the step-11 label stay valid.
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
Steps 01 to 10 (or a written amendment naming what is unavailable): the acceptance run includes GA11, which needs the recovery and performance work of Step 10. Policy-independent scaffolding may start after the overall start conditions; decision-dependent behaviour and its final oracle stay blocked until the named authority decides. Proposed defaults are recommendations, never prerequisites. Blocked decisions: GL01-staged, GL02-staged, GL03-staged, GL04-staged, GL05-staged, GL06-staged, GL07-staged, GL08-staged, Q11.
Changes (illustrative, not a final schema)
Sources: Blueprint pages cited per item (GGA-Requirement-Register).
Build items:
- Acceptance run of GA01 to GA12 with synthetic data; permissions and failure cases included (p. 18)
- Recheck, on the integrated build, of every scenario that depends on later components (Dependency-and-Regression-Table)
- Definition of ready to pilot: no unresolved access-control defect; named operations and technical owners trained; email and invoice flows demonstrated; backups and monitoring work; funded pilot budget and launch decisions recorded; export documented (p. 18)
- Coverage disposition for language and email: A11-Language-and-Email-Checklist
- Separate written launch approval (not a software test result)
Expected outputs and invariants
A scenario is recorded Passed only for a named integrated build and fixture; evidence for manual procedures stays separate.
Tests-first subset
Primary scenarios of this step (write these tests first): none.
Assertions to write first: new GGA scenarios none. No legacy scenario has this step as its primary step.
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 Blocked by that 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
Scenarios (of any step) that can only be completed or rechecked once this step exists:
- Every scenario with a later-step entry in Dependency-and-Regression-Table is rechecked here on one named integrated build.
Decisions GGA must settle (dependent behaviour stays blocked until the named authority decides)
GL01-staged, GL02-staged, GL03-staged, GL04-staged, GL05-staged, GL06-staged, GL07-staged, GL08-staged, Q11
Exit evidence
All twelve gates have evidence on one named build, or a written amendment names what is tested and what is unavailable; it is never presented as an unchanged pass.
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).
Coverage disposition for language and email
Use A11-Language-and-Email-Checklist. Japanese and Korean content is stored and displayed as Unicode; a multilingual interface is not required in the first release (p. 10). English interface and the agreed safe email templates have only proposed, Not executed checklist coverage.
Navigation: Step-10-Hardening-and-Operations ← this step → Step-12-Manual-DG-Services-and-Scope-Guards · Implementation-Order-Overview