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.
Q07 · Revocation and notification contract
| Field | Value |
|---|---|
| Status | Pending GGA decision (recorded in 1.3 as “Pending DG decision”) |
| 1.3 to GGA disposition | Reframed |
| Responsible role to confirm (recommendation) | GGA operations + delivery lead |
| Needed before | Before T25–T26, T33–T36 |
| Named owner | [ ] |
| Due date | [ ] |
| GGA approver / decision date / chosen rule | [ ] |
What the GGA documents say
Release re-checks both consents, authorisation, active listing and applicant eligibility in one transaction; withdrawal rules before and after release; recipient and scope re-checked before delivery; retry 1 min, 5 min, 30 min, 2 h (proposed) then an operations exception queue; reconcile uncertain delivery; failures never bypass consent (pp. 6, 15, 16).
Source class: client-supplied design proposal or proposed default unless stated; GGA acceptance is not recorded. See GGA-Requirement-Register.
Rule or question as proposed in 1.3 (kept as history)
Name current recipient, final eligibility boundary, retry/lease limits, ambiguous-send handling and manual recovery owner.
Still open
Who is the named failed-delivery handler (operations owner, GL01) and the final eligibility boundary wording for in-flight work.
Scenarios that depend on this decision (1.3 IDs, unchanged)
T04, T09, T16, T18, T19, T25, T26, T32, T33, T34, T35, T36. Their dispositions are set in work package R4.
Related
GL01-staged. Index: Decision-Index.
A suggested default is a recommendation, not an approval. Record any actual decision with: ID · chosen rule · amendment to architecture and acceptance · GGA approver · decision date · affected test IDs · implementation owner.