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.
Deployment, recovery and ownership
Sources: Blueprint pp. 11, 17, 19, 20 (GGA-Requirement-Register). Vendor-neutral. GGA owns the repository and holds the infrastructure and service accounts under its control; providers, region and costs are GGA launch decisions made with the developer (p. 20).
flowchart LR SC[Version-controlled source + reviewed migrations] --> CI[CI: tests, build, dependency checks] --> ST[Staging<br/>synthetic data] --> AC[Acceptance gates GA01 to GA12<br/>and launch decisions recorded] --> PR[Production<br/>app, worker, database, private storage] --> OP[Backups, monitoring, rollback]
| Area | Plan or evidence |
|---|---|
| Environments | Separate development, staging, production; no real data in staging until GGA’s data policy exists |
| Deployment and rollback | Reviewed migrations, rollback procedure, dependency checks, alert to the technical owner. Kept from 1.3 where not in conflict: reversible rollout where feasible, a migration backup or forward-recovery plan, smoke checks after deployment, documented rollback decisions |
| Operations | Monitor errors, unauthorised access attempts, job age, queue failures, delivery failures, storage, provider usage and monthly service cost (never private bodies in logs); member-impacting incidents go to operations with a named communication owner |
| Backup and recovery (proposed) | Daily backups, 24-hour recovery point, 8-hour restoration objective; encrypted, access restricted; restore demonstrated in staging before launch and repeated monthly during the pilot |
| Performance (proposed test) | 100 companies, 1,000 listings, 25 concurrent users; 95% of core page and API responses under 2 seconds excluding external delivery |
| Security services | Mature authentication, MFA for privileged staff, least-privilege database credentials (row security, if used, tested with the real application role), private object storage, upload scanning, encrypted connections, secret management |
| Handover | GGA-owned repository, build and deploy instructions, dependency inventory, accounts under GGA control; migrations, field dictionary, API contract, permission policies, sample data, automated acceptance tests; operations guide; monitoring, restore evidence, incident contacts, rollback; configuration register; monthly recurring-cost estimate; essential business records exportable in a documented format |
The 99.5% monthly availability figure in the 1.3 proposal is not in the GGA documents and is not carried forward.
Retained from revision 1.3
Release sequence with staging evidence and separate written launch approval; no deployment on silence; no private bodies in logs; separate credentials per environment; restore must be demonstrated, not assumed.
Open
Hosting, region, authentication, email, file scanning, database and backup providers and the cross-border sharing arrangements are launch decisions for GGA (Blueprint pp. 17, 20). Named operations owner and backup, data owner and finance owner are needed before launch.