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.
Provisional schedule — non-binding
Sources: Blueprint pp. 19, 20 (GGA-Requirement-Register). The 1.3 schedule addendum covered the old scope; it is kept as history below. No GGA calendar exists. The Blueprint says to obtain a fixed scope, estimate and support arrangement after the launch decisions are recorded.
What can be stated now
- Five stages with exit conditions: see Delivery-Options-Comparison. Stage dates are unset.
- Fixed commitments (Blueprint p. 1): one online session every two weeks and one major event every six months, the event with a funded plan before commitments (p. 9). Proposed (p. 16, 17): monthly restore rehearsal during the pilot; outcome prompts 14 and 45 days after introduction.
- Anand’s fortnightly hosting is about 26 hours a year before preparation, partner work and events; the full time requirement is tracked and operations are funded from an explicit budget.
Long-lead items (updated)
GGA-owned accounts and billing; hosting region and providers (authentication, email with a verified sender domain, file scanning, database, backup); production domain, DNS and TLS; named operations owner and backup, finance approver, data owner, event lead and technical owner; privacy notice and cross-border sharing arrangement; partner onboarding criteria and agreements; funded pilot and event budget.
Open inputs
Staffing and leave, review windows, launch decisions GL01 to GL08, retention periods, tax presentation and invoicing entity, the first set of country partners and categories.
History: the 1.3 provisional schedule (superseded)
About 8 to 10 weeks to launch readiness for the Balanced private exchange with two engineers and one testing week; milestone bands staging demo 1–2, core workflows 3–4, approvals and notifications 5–7, ready for testing 6–8, engineering completion 7–9 weeks; proposed review windows one business day for routine decisions and five business days for consolidated feedback; independent QA not included; one engineer roughly 13–18 active weeks. Originals: 10-Sources/originals/provisional-schedule.pdf and .html. The base was 5.4 to 7.5 weeks of active engineering plus one shared contingency of 1.1 to 1.5 weeks, counted once; waiting time on the client side was additional; delays added time; go-live needed separate written approval; independent QA was not included and, if required and serial, allowed a provisional 1 to 2 elapsed weeks. Long-lead items then included a verified sender domain (SPF and DKIM). These figures do not apply to GGA.