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.
Acceptance gates
Sources: Blueprint p. 18 (GGA-Requirement-Register) and the 1.3 gates A01 to A11. The old IDs A01 to A11 never change; the Blueprint’s tests A1 to A12 become GA01 to GA12 so the two sets cannot be confused. “Scoped” means a written amendment naming what is tested and what is unavailable; it is never presented as an unchanged pass.
Demonstrate the complete journey with synthetic data before inviting the first 20 companies. Passing screens alone is insufficient; permissions and failure cases must pass too.
GGA gates (Blueprint A1 to A12)
| Gate | Expected result | Evidence needed |
|---|---|---|
| GA01 Public and private views | A visitor sees only approved summaries; direct API calls, source HTML, caches and file URLs reveal no member or restricted content | Named build; response and cache inspection |
| GA02 Required profile | Missing revenue period, capability evidence or accountable owner prevents eligibility; the form states exactly what to correct; drafts stay saved | Named build |
| GA03 Freshness boundary | At due plus 14 days new detailed access pauses even if the scheduled job failed; a valid attestation restores access immediately unless an independent hold exists | Clock-controlled test with the job disabled |
| GA04 Publication control | A partner cannot self-approve, view another partner’s pipeline or edit another owner’s listing; a changed or expired offer cannot accept new pitches | Named build |
| GA05 Scoped sharing | The owner sees only the applicant-approved fields; no contacts before both current approvals; withdrawal or package change invalidates pending consent | Named build; canary fields |
| GA06 Concurrency and retries | Two simultaneous accepts create one introduction; replayed jobs create no second grant, invoice or term; a failed notification leaves a recoverable task | Race harness; failure injection |
| GA07 Payment independence | An eligible company that declines contribution keeps access (it can still lose eligibility through incomplete or overdue data or an administrative hold); a paid company with overdue data is paused; a partner-reported deal cannot trigger an invoice | Named build |
| GA08 Event behaviour | Duplicate registration blocked; concurrent requests cannot exceed capacity; cancellation, waitlist, timezone and changed-occurrence reminders behave as specified | Named build |
| GA09 Tenant and role isolation | Changing a company or file ID exposes nothing; finance cannot read capability files; non-finance users cannot record a settlement | Canary fixture |
| GA10 Files and AI | Unscanned or disallowed files cannot be shared; AI drafts stay unpublished until confirmation; AI cannot grant access or decide contribution status | Named build |
| GA11 Operations and recovery | Operations resolve a review, a failed message and an expired consent without Anand; a backup is restored in staging; the proposed performance scenario is measured | Restore record; measurements |
| GA12 Commercial end to end | Company confirms value, opts in, receives a finance-approved invoice and settles; one dated 12-month term appears; expiry neither auto-charges nor removes eligibility | Named build |
Definition of ready to pilot: all gates pass on a named integrated build; no unresolved access-control defect; named operations and technical owners trained; email and invoice flows demonstrated; backups and monitoring work; a funded pilot budget and the launch decisions recorded; the owner can export essential business records in a documented format. Release gate carried from 1.3 as a Proposed carry-forward (GGA states only that no access-control defect may remain unresolved and that launch decisions are recorded): no unresolved critical or high security defect; separate written launch approval.
What happens to the 1.3 gates
| Old gate | Disposition | Replaced or carried by |
|---|---|---|
| A01 publish and find | Reframed | GA01, GA04 (operations review; public summaries) |
| A02 respond without posting | Reframed: pitch against a specific opportunity; the private question without posting has no GGA feedback and stays a Proposed carry-forward | GA05 |
| A03 independent discussions | Reframed | GA05, GA09 (applicants isolated from each other); discussion threads are a Proposed carry-forward, no GGA feedback |
| A04 delegated approval | Proposed carry-forward for company roles; operations review replaces publication approval | GA04 |
| A05 version changes | Reframed: a material edit pauses the listing until re-approved | GA04 |
| A06 scoped revocation | Retained | GA05, GA09 |
| A07 scoped lifecycle | Reframed | GA04, GA06 (expiry, pause, close) |
| A08 scoped failure | Retained | GA06 |
| A09 scoped privacy | Retained and extended to the three layers | GA01, GA09 |
| A10 scoped readiness | Retained; targets now proposed in the Blueprint | GA11 |
| A11 language | Reframed: English default, Unicode storage, no multilingual interface in release one | A11-Language-and-Email-Checklist |
| (new) | No 1.3 equivalent: profile completeness, freshness, payment independence, events, files, commercial end to end | GA02, GA03, GA07, GA08, GA10, GA12 |
Scenario traceability: Traceability-Matrix (rewritten in work package R4).