Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
T28 · DG operations do not grant private-message browsing
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | API · security · audit |
| Priority | P0 |
| Gates | A06, A09 |
| Build step | Step-03-Policy-Pipeline-and-Isolation-Harness |
| Decisions | Q08 |
Given
DG has approved membership/operational tools and admin MFA; B/C private canaries exist.
When
DG opens routine metadata views and attempts private-body routes; exercise any expressly approved support-access path.
Then / oracle
Candidate routine DG allowlist: opaque record/event IDs, approved event/state labels and timestamps only. Exclude bodies, terms, decline reasons and contact data. Company/participant identifiers await Q08. Private-body routes deny by default. Any approved support exception is scoped, time-limited, authorised and audited; otherwise disabled.
Evidence required
Field-by-field metadata allow/deny tests; synthetic bodies/terms/reasons/contacts absent; support grant/revoke audit if approved.
Decision dependency (verbatim)
Q08: final metadata/identifier allowlist and support authoriser/scope/expiry. Candidate is not approved production data access.
Source: TDD rev 1.3 (PDF); machine-readable in 10-Sources/tdd-bundle/. Back to Scenario-Index · Traceability-Matrix · integration dependencies in Dependency-and-Regression-Table.