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.

GGA traceability matrix

How the Blueprint pages, the gates GA01 to GA12, the decisions and the scenarios connect. The legacy Traceability-Matrix (1.3 gates A01 to A11 and build steps) stays as history until the build order is rebuilt from the Blueprint stages in R5; “Needs build” means real application adapters and has not happened.

Blueprint page to scenarios

Every Blueprint page that states a testable rule has at least one scenario; pages 12 and 13 (data model) are tested through the scenarios that exercise their constraints.

Blueprint pageTopicGS scenariosLegacy scenarios with a disposition on this page
p. 1Scope, commitments, build and deferGS01-staged, GS25-stagedDG01, DG24, DG33, DG34, DG36, DG41, DG44, T09, T11, T12, T24
p. 2Service journeyGS24-staged, GS32-stagedDG02, DG14, DG28
p. 3Roles, access and eligibilityGS01-staged, GS05-staged, GS08-staged, GS14-staged, GS17-staged, GS20-staged, GS26-stagedDG05, DG22, DG26, T01, T02, T03, T26, T28
p. 4Onboarding and dataGS03-staged, GS04-staged, GS07-staged, GS19-staged, GS32-stagedDG02, DG25, DG26, DG27, DG28, DG35, T01, T03, T04, T08, T37
p. 5Opportunity intake and publicationGS01-staged, GS02-staged, GS08-staged, GS09-staged, GS32-stagedDG02, DG15, DG29, DG30, DG37, DG38, DG39, DG42, T05, T13, T14, T15, T21, T22, T23
p. 6Introductions and consentGS10-staged, GS11-staged, GS24-stagedDG04, DG06, DG07, DG08, DG10, DG11, DG16, DG20, DG21, T10, T16, T17, T18, T19, T20, T22, T25, T29
p. 7Profile updates and matchingGS05-staged, GS06-staged, GS14-staged, GS19-staged, GS28-stagedDG03, DG05, DG27, DG29, T06, T07, T26, T31
p. 8Value and annual contributionGS14-staged, GS22-staged, GS23-staged, GS24-stagedDG01, DG14, DG15, DG16, DG19, DG33
p. 9Sessions, events, ownershipGS15-staged, GS16-staged, GS20-stagedDG09, DG12, DG18, DG31, DG32, DG34, DG43
p. 10Screens and behaviourGS01-staged, GS03-staged, GS04-staged, GS10-staged, GS13-staged, GS14-staged, GS15-staged, GS22-staged, GS28-staged, GS29-staged, GS31-stagedDG25, DG37, DG40, T01, T05, T08, T11, T30, T34, T39
p. 11System architectureGS13-staged, GS19-staged, GS30-stagedT06, T33, T38
p. 12Core data relationshipsGS12-staged, GS17-stagedT14, T18, T32
p. 13Data dictionaryGS03-staged, GS07-staged, GS08-staged, GS17-stagedT02, T04
p. 14API contractGS01-staged, GS03-staged, GS04-staged, GS07-staged, GS08-staged, GS10-staged, GS12-staged, GS17-staged, GS18-staged, GS22-staged, GS23-stagedDG17, DG25, T01, T05, T08, T13, T15, T17, T18, T23, T37
p. 15Transaction and state rulesGS07-staged, GS11-staged, GS12-staged, GS13-staged, GS15-staged, GS17-staged, GS22-staged, GS23-stagedDG04, DG10, DG11, DG17, DG19, T15, T16, T19, T25, T27, T32, T33
p. 16Automation and integrationsGS06-staged, GS09-staged, GS13-staged, GS16-staged, GS19-staged, GS20-staged, GS24-staged, GS25-staged, GS29-stagedDG13, DG23, DG24, DG38, DG44, T21, T23, T29, T31, T34, T35, T36
p. 17Security, privacy, reliabilityGS01-staged, GS02-staged, GS05-staged, GS11-staged, GS13-staged, GS17-staged, GS18-staged, GS21-staged, GS26-staged, GS27-staged, GS30-stagedDG20, DG21, DG22, DG40, DG42, T02, T10, T11, T25, T26, T27, T28, T34, T37, T38, T39, T40
p. 18Acceptance tests and release gateGS20-staged, GS21-staged, GS27-stagedT13, T40
p. 19Delivery plan and handoverGS21-staged, GS24-stagedDG15, T40
p. 20Launch decisionsnone (decisions, not behaviour): GL01-staged to GL08-staged—

Gate to scenarios

See the coverage table in GGA-Scenario-Index. Gates are defined in Acceptance-Gates-A01-A11.

Decision to scenarios

Only decisions that leave an assertion open appear.

Honesty

A mapping is an index, not proof. It does not show that the Blueprint cites a test, that a decision is made, or that anything ran. Requirement-level coverage (each of the 174 requirements to a behaviour note, scenario, gate, decision or recorded deferment) is checked by the baseline validator in R7 against GGA-Requirement-Register.