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.
DG04 · Named introduction needs independent exact consents
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Manual DG service |
| Layer / kind | Manual · consent rehearsal |
| Priority | — |
| Gates | S02 |
| Build step | Step-12-Manual-DG-Services-and-Scope-Guards |
| Decisions | Q14 |
Given
A wants B contact; B has not consented or consent is for different recipient/purpose.
When
Request each authority separately, then simulate both yes, one no, silence and expired consent.
Then / oracle
Share only exact fields to approved counterparty for purpose/period with current authority. Silence is not consent. If no valid bilateral release, no introduction occurs. Same reply regardless of hidden status: No introduction is arranged under this request. We do not disclose other companies’ responses or whether any were sought.
Evidence required
Separate consent records; final recipient/payload check; messages for all variants; no leaked candidate identity/count.
Decision dependency (verbatim)
Q14: authority, approved channel, fields, expiry, revocation and proof.
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.