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.
GS30 · Environment separation and release discipline
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software (new in the GGA baseline) |
| Source | Blueprint pp. 11, 17 (GGA-Requirement-Register); client-supplied draft, not accepted |
| Gate | GA11 |
| Blueprint delivery stage | Stage 4 Pilot with 20 companies (p. 19) |
| Build step | 01 (primary; tests first) |
| Replaces or carries | T38, T40 |
| Decisions | GL07-staged |
Given
Development, staging and production environments, a pending migration and a failing deployment.
When
Deploy through staging; run a migration review; roll back; inspect error and queue monitoring; check dependency and cost reporting.
Then / oracle
Environments are separate with managed backups, private object storage, encrypted connections and secret management. Migrations are reviewed and a rollback procedure exists. Errors and queue age alert the technical owner; member-impacting incidents route to operations with a defined communication owner. Dependency checks run. No real data enters any environment before GGA’s data policy is recorded.
Evidence required
Release record, rollback evidence and monitoring screenshots for the named build.
Decision dependency
- GL07-staged: Provider choice and the support arrangement are launch decisions
Where a decision is pending, the dependent assertion is Blocked by that decision and no oracle is invented. A proposed default is a configuration value, not a promise. This note is a specification: it is Passed only on a named integrated build and fixture.
Back to GGA-Scenario-Index · GGA-Traceability-Matrix · Scenario-Dispositions.