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.

DG04 · Named introduction needs independent exact consents

FieldValue
StatusNot executed
TypeManual DG service
Layer / kindManual · consent rehearsal
Priority—
GatesS02
Build step06 (GGA order; the 1.3 step is history)
DecisionsQ14

Disposition under GGA

FieldValue
DispositionReframed
GGA basisBlueprint pp. 6, 15 (GGA-Requirement-Register)
Replaced or carried byGS11-staged
Still opennone
What changesA named introduction needs two independent, exact consents bound to scope and version.

The 1.3 text below is kept verbatim as history. Where the disposition is Reframed, Superseded or Parked it is not the GGA oracle; use the replacing scenario. A Parked scenario has no GGA feedback and stays a Proposed carry-forward. The status stays Not executed. Register: Scenario-Dispositions.

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.