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.

Tier differences and the GGA release scope

The 1.3 vault compared three delivery options (Optimized, Balanced, Comprehensive). The GGA documents replace that comparison with one first release and an explicit deferral list (Blueprint p. 1; GGA-Requirement-Register). This note maps every 1.3 capability row so nothing is lost.

Build now (Blueprint p. 1)

Registration, profiles, public and member views, partner intake, moderation, introductions, reminders, sessions, outcome records and contribution tracking. Start with 20 companies; validate the complete workflow before expanding towards 100.

Defer until the model is proven (Blueprint p. 1)

Native mobile apps, a general social feed, open direct messaging, automated deal negotiation, complex recommendation models, a full accounting system, automatic LinkedIn publishing, WhatsApp automation and AI matching.

Where each 1.3 capability stands

1.3 capability1.3 tierGGA status
Fixed roles, one company per userBalancedReplaced: role set and one selected company context per session; colleague invitations supported
Multi-company users with an explicit active companyComprehensiveData model allows invited colleagues; multiple memberships per user is open question N9
Named-member audienceBalancedReplaced by public, member and restricted layers
Selected-company audiences and exclusionsComprehensiveNo GGA feedback; Proposed carry-forward, outside release one
Hidden identityComprehensivePartly answered: public summaries are anonymous and names appear only when explicitly approved; counterparty identities are restricted material (Blueprint p. 5)
Version-aware approvals, immediate emailBalancedReframed: operations review; non-sensitive job-driven messages
Daily pending and overdue viewBalancedReframed: member dashboard and operations queues (Daily-Tracking)
Digests, quiet hours, agreed escalationComprehensiveNo GGA feedback; Proposed carry-forward
Rule-based discovery, no AIBalancedRetained: rule filters with reasons; AI deferred
AI drafts and explanationsComprehensiveOptional drafting, summary, translation and field suggestions are allowed if saved separately until approved; AI matching is deferred; AI never alters eligibility, publishes, shares contacts, sends outreach or approves fees (Blueprint p. 7)
Japanese translation, hidden identity, SSOConditionalUnicode storage and language preference now; translated interface later; SSO not mentioned
80% usefulness gateComprehensiveNo GGA equivalent; the pilot metrics on Blueprint p. 19 apply instead

Moving an item from a deferral list into release one is a scope change needing re-estimation (see Delivery-Options-Comparison). The scope-guard idea from 1.3 (DG24, DG44) stays: ideas that are deferred are tested for silent expansion.