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.
Implementation order
Twelve ordered steps, rebuilt from the Blueprint’s delivery stages (p. 19). They declare what to build, in which order, with which tests first; they do not start coding. Order rationale: identity, profile and eligibility first because every later feature depends on them and on the policy pipeline; the transactional-outbox contract in the foundation so every event-producing mutation uses it; the worker after the records it announces; operations, finance and the acceptance run last. Step numbers and file names are stable identifiers kept from revision 1.3 (like the historical DG prefix); titles and scope are rewritten.
Blueprint stages and the steps that serve them
| Blueprint stage | Deliverable (p. 19) | Exit condition (p. 19) | Steps |
|---|---|---|---|
| 1 Confirm and design | User flows, screen sketches, field dictionary, access matrix, configuration defaults, chosen stack | GGA approves rules, ownership, budget and pilot scope | No build step. A GGA approval that precedes Step 01; the vault’s Stage 1 inputs are the field dictionary in Blueprint p. 13, the access matrix in p. 3 and the launch decisions GL01 to GL08. |
| 2 Foundation and publishing | Authentication, company profiles, public and member projections, partner intake, operations review | An eligible company can discover a reviewed offer; isolation tests pass | Steps 01 to 05 |
| 3 Complete the service loop | Interest, scoped consent, introduction, profile reminders, events, outcomes, contribution records | A synthetic company completes the end-to-end journey including a payment decline | Steps 06 to 09; the Stage 3 exit evidence is the synthetic end-to-end run in Step 09 (GS22 to GS24, including a payment decline) |
| 4 Pilot with 20 companies | Production monitoring, operational training, staffed support, live country-partner sourcing | Real usage shows profiles stay current and the operations owner can follow through | Step 10 (readiness) and Step 11 (the A1 to A12 acceptance run and the gate before inviting the first 20 companies); the pilot itself is an operating activity, not a build step |
| 5 Expand towards 100 | Address demonstrated bottlenecks; improve search and workflow convenience | Affordable service; introductions produce reported value; founder time within the agreed cap | No build step; new work is a scoped change request |
Stage dates, fees and staffing are open (Provisional-Schedule, Delivery-Options-Comparison). The Blueprint says to obtain a fixed scope, estimate and support arrangement after the launch decisions are recorded.
Steps
Every one of the 116 scenarios (84 legacy and 32 GGA) is the tests-first subject of exactly one step. Legacy scenarios that are Superseded or Parked sit in Step 12 with no build and no oracle. The GS “Blueprint delivery stage” is the stage by which the full variants are expected to be exercised; the primary step is where the tests are written first, so it can be earlier.
How to read the order
- The primary-step mapping is an index, not proof that a full scenario can be completed there. Many scenarios need components from later steps; see Dependency-and-Regression-Table. Each step lists its deferred integration checks and the earlier scenarios it lets you finish.
- A software scenario’s full status cannot be recorded as Passed until every relevant variant has been exercised on a named integrated build (Step-11-UAT-and-Release). Operating-procedure evidence names the procedure revision, synthetic fixture, staff roles, date and observed result; mixed cases need both evidence streams (Mixed-Evidence-Disposition, Scenario-Dispositions).
- Operating procedures are a parallel track (Step 12) that needs no application build; their approval is a pre-real-data gate owned by GGA, not a software gate.
Preconditions before any step
- A proposed default is a recommendation, never a prerequisite: policy-independent scaffolding may start after the overall start conditions, but decision-dependent behaviour and its final oracle stay blocked until the named authority decides.
- Launch decisions GL01 to GL08 recorded before production launch, and the ones named in each step before that step’s dependent behaviour (Decision-Index).
- A statement of work, GGA-owned accounts, hosting region and providers chosen, named acceptance reviewer and launch approver. Two dedicated engineers is an assumption, not a fact. Fees and dates are open.
- No real GGA or member data in any environment before GGA’s data policy is recorded.
Rules for every step
- Test first; keep scenario IDs stable.
- Deny by default; check authorisation on every read, mutation, search, count, export, file download and job.
- A scenario with a pending decision is not given an invented oracle; it is Blocked by that decision.
- Software evidence names the build and fixture; authored Gherkin is not a passing suite.
- Software scope changes need a written change request; deferred items stay deferred (GS25-staged).
Traceability: GGA-Traceability-Matrix (GGA) and Traceability-Matrix (1.3 history).