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.
DG07 · Unanswered-item help is requester-authorised
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Manual DG service |
| Layer / kind | Manual · communication rehearsal |
| Priority | — |
| Gates | S03 |
| Build step | Step-12-Manual-DG-Services-and-Scope-Guards |
| Decisions | Q14, Q15, Q08 |
Given
B deliberately requests help and supplies own reference plus approved neutral text; DG holds only opaque platform metadata.
When
Verify B authority, approved contact route and current A contact permission; prepare outreach.
Then / oracle
DG does not resolve an opaque ID to identify A or retrieve messages. Contact uses deliberately supplied, permitted case information and known authorised route. Only approved neutral text is sent; no promise A will answer. A may ask its own admin for reassignment help.
Evidence required
Request, text consent, trusted contact source, staff owner and send/cancel record; no private-body fetch.
Decision dependency (verbatim)
Q14/Q15: contact basis, follow-up/close windows; Q08 grants no implicit mapping.
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.