Status. Proposed engineering reference derived from vault revision 1.3. Every scenario is Not executed; no application exists. Generated from the scenario notes; regenerate rather than hand-edit.

Coverage matrix

Coverage here means which scenarios are planned against a module or gate. It is not a pass record. The owning view is Traceability-Matrix; this note re-slices it by module and gate.

Module by primary step

ModuleStepsScenarios (primary step)
Identity and company access01, 02, 03T01, T02, T03, T04, T16, T25, T26, T27, T28, T37, T38, DG22, DG25, DG26
Opportunities and discovery04, 05T05, T06, T07, T08, T13, T14, T15, T21, T22
Engagement and tracking06, 08T09, T10, T11, T12, T17, T18, T19, T20, T23, T24, T29, T30, T31, T32
Notifications and administration07, 09T33, T34, T35, T36
Hardening and release (cross-cutting)10, 11T39, T40
DG manual services (not software)12DG01, DG02, DG03, DG04, DG05, DG06, DG07, DG08, DG09, DG10, DG11, DG12, DG13, DG14, DG15, DG16, DG17, DG18, DG19, DG20, DG21, DG23, DG24, DG27, DG28, DG29, DG30, DG31, DG32, DG33, DG34, DG35, DG36, DG37, DG38, DG39, DG40, DG41, DG42, DG43, DG44

Gate by scenario

Gate meanings: Acceptance-Gates-A01-A11 (A) and DG-Services-Index (S). Gates A06, A09, A10, A11 carry scoped or unverified boundaries; read the gate note before counting coverage.