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.
Q11 · Acceptance and start/launch authority
| Field | Value |
|---|---|
| Status | Pending GGA decision (recorded in 1.3 as “Pending DG decision”) |
| 1.3 to GGA disposition | Reframed |
| Responsible role to confirm (recommendation) | GGA decision-maker + developer |
| Needed before | Before UAT/release; scope/commercial agreement before build |
| Named owner | [ ] |
| Due date | [ ] |
| GGA approver / decision date / chosen rule | [ ] |
What the GGA documents say
Acceptance is the twelve tests A1 to A12 (vault GA01 to GA12) plus the definition of ready to pilot; separate launch decisions are recorded before launch (pp. 18, 20).
Source class: client-supplied design proposal or proposed default unless stated; GGA acceptance is not recorded. See GGA-Requirement-Register.
Rule or question as proposed in 1.3 (kept as history)
Named reviewer/launch approver, defect criteria, review window and evidence sign-off; separate written go-live approval.
Still open
Named acceptance reviewer, launch approver, defect criteria and review window.
Scenarios that depend on this decision (1.3 IDs, unchanged)
T40. Their dispositions are set in work package R4.
Related
GL01-staged, GL02-staged. Index: Decision-Index.
A suggested default is a recommendation, not an approval. Record any actual decision with: ID · chosen rule · amendment to architecture and acceptance · GGA approver · decision date · affected test IDs · implementation owner.