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.
GS11 · Consent, release and withdrawal
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software (new in the GGA baseline) |
| Source | Blueprint pp. 6, 15, 17 (GGA-Requirement-Register); client-supplied draft, not accepted |
| Gate | GA05, GA06 |
| Blueprint delivery stage | Stage 3 Complete the service loop (p. 19) |
| Build step | 06 (primary; tests first) |
| Replaces or carries | DG04, DG07, DG08, DG10, DG11, DG20, DG21, T16, T19, T25, T32 |
| Decisions | GL04-staged |
Given
A pending introduction exists after the owner accepts a pitch. Consent requests are open to both parties with an expiry.
When
Release with one approval only; change the package; withdraw before release; let a request expire; operations tries to consent for a participant; both approve while a user is deauthorised or the listing is paused; withdraw after release.
Then / oracle
No contact is released before both current approvals. Each approval binds the introduction, recipient, fields and files, purpose, version and expiry; changing the package invalidates prior approvals. Release re-checks both approvals, both users’ authority, an active listing and applicant eligibility in one transaction, releases once and queues one delivery per recipient. Decline, timeout and withdrawal close without releasing. Operations may remind but cannot consent on behalf. After release future portal access is revoked where possible and history shows what was already shared.
Evidence required
Release record count per introduction; consent rows by version; contact canaries absent until release; history after post-release withdrawal.
Decision dependency
- GL04-staged: The 14-day consent expiry is a proposed default; retention periods and the withdrawal path are for the GGA data owner
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.