Status. Draft staging note for work package R1. It moves to 01-Overview/ once the owner override is active. The Concept Note and Blueprint are marked v1.0 (20 October 2026); the Idea and the Concept and Architecture file carry no version marker. All four are client-supplied and GGA acceptance of them is not recorded. No scenario has been executed.

GGA source digest

The four client documents received on 20 October 2026. They sit on top of the earlier vault wherever they speak. Text extracts used for review are in docs/extracted/.

File	Short name	Bytes	SHA-256	What it covers
docs/high-level-idea.md	Idea	2746	7b418eecadbea1f11cabb28f85ff40abfd9a66008b42771725a953e76b3019cb	Three paragraphs: the owner’s summary of the concept, the exchange, contribution and operating model
docs/GGA_Concept_Note.pdf	Concept Note (CN)	339740	911d81c89820415cc4977cc955b63292c67d9356bae3994985aa45fc221a9938	2 pages, v1.0, 20 Oct 2026: what GGA provides, how the exchange works, the personal commitment, flow diagram
docs/GGA_Concept_and_Architecture.docx	Concept and Architecture (CA)	359038	26133d63882fc678148b4be940f264c0429b2e5a3c3cae0d86a07d7b7a61b0a8	Concept outline table, exchange of value, access levels, required company data, update policy, fees after value, operations and owners, opportunity workflow, first release, operating discipline
docs/GGA_Development_Blueprint.pdf	Development Blueprint (BP)	134087	ca3ddfdca00fad7301925181481c9e184eb794e64ae5f40138c9b4370d28cfd5	20 pages, v1.0, 20 Oct 2026: see the page map below

Blueprint page map

Page	Topic	Requirement areas
1	Purpose, six requirements to preserve, build now versus defer	Programme, Scope
2	Service journey; what the system records at each stage; review is not verification	Programme, Opportunity, Contribution
3	Roles and access rules; eligibility expression; server-side checks	Access
4	Company onboarding and data; profile versions	Profile
5	Opportunity intake, layers, lifecycle, categories, publication controls	Opportunity
6	Introductions and consent; rules for the developer	Introduction
7	Profile updates, freshness, matching, optional AI	Freshness, Matching
8	Value and annual contribution	Contribution
9	Sessions, events, ownership	Sessions
10	Screens and user behaviour; interaction standards; language	Screens, Scope
11	System architecture and boundaries	Architecture
12	Core data relationships and integrity rules	Data
13	Data dictionary and constraints	Data
14	API endpoint contract	API
15	Transaction and state rules; status codes; idempotency	Transactions, API
16	Automation and integrations; retry policy	Jobs
17	Security, privacy, reliability, targets	Security
18	Acceptance tests A1 to A12 and release gate	Acceptance
19	Delivery plan, handover package, pilot metrics	Delivery
20	Launch decisions and technical references Blueprint-T1 to T3	Launch decision

Blueprint references T1 to T3 (OWASP Authorization, OWASP File Upload, PostgreSQL Row Security) are cited only as Blueprint-T1, Blueprint-T2, Blueprint-T3; they are not scenario IDs and must never be confused with the earlier vault’s T01 to T40.

Known differences between the four documents

Topic	Difference	Proposed handling
Who submits listings	Idea: independent country partners and participating companies submit. Blueprint p. 13: only an approved partner may publish through review; p. 14: partner approval or eligible company status	Open question N9. Treat both as allowed until the client confirms
Registered but incomplete or overdue companies	CA: public summaries remain available; detailed access locked or paused. Blueprint p. 3 adds existing introduction history, outcomes and contribution records for overdue companies	Blueprint is more detailed; it governs
Event registration for overdue companies	Blueprint p. 3 blocks new registrations for incomplete data; p. 9 keeps existing registrations valid when a profile later becomes overdue	Both stand; they cover different cases
Opportunity categories	Idea: distribution, partnerships, services, technology, IP, talent, investment, other approved. CA adds market entry, products, expertise. Blueprint p. 5: distribution, sourcing, market entry, services, technology, IP, talent, investment, other approved (configurable)	Treated as one configurable list; union recorded in the register; operations enables categories (launch decision)
Company context	Blueprint p. 4: one selected company context per session, colleague invitations supported	Open question N9: multiple memberships per user

Source precedence rule (proposed): the Blueprint governs over the Concept and Architecture, the Concept Note and the Idea where they differ; every discrepancy is listed for the client.