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.
GS29 · Dashboards and consoles mirror authorised records
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software (new in the GGA baseline) |
| Source | Blueprint pp. 10, 16 (GGA-Requirement-Register); client-supplied draft, not accepted |
| Gate | GA09, GA11 |
| Blueprint delivery stage | Stage 3 Complete the service loop (p. 19) |
| Build step | 08 (primary; tests first) |
| Replaces or carries | T30 |
| Decisions | GQ04-staged |
Given
A member with pending consent requests, upcoming sessions and an introduction in progress. An operations console with queues.
When
Open the member dashboard and each console queue as the allowed role and as other roles.
Then / oracle
The member dashboard shows profile status, relevant opportunities, upcoming sessions, pending consent requests and introduction progress, with contribution as a separate status. Operations and finance queues show owner, age, next action and audit history and no content the role may not read. Every restricted screen explains the next action in plain language.
Evidence required
Dashboard items compared with the underlying authorised records; queue content per role.
Decision dependency
- GQ04-staged: Private questions, discussions and next actions have no GGA feedback; their dashboard items are not asserted here
Where a decision is pending, the dependent assertion is Blocked by that decision and no oracle is invented. A proposed default is a configuration value, not a promise. This note is a specification: it is Passed only on a named integrated build and fixture.
Back to GGA-Scenario-Index · GGA-Traceability-Matrix · Scenario-Dispositions.