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.
T16 · Approval and role revocation races remain authorised
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | API · database · race injection |
| Priority | P0 |
| Gates | A04, A06 |
| Build step | 06 (GGA order; the 1.3 step is history) |
| Decisions | Q07 |
Disposition under GGA
| Field | Value |
|---|---|
| Disposition | Retained and refined |
| GGA basis | Blueprint pp. 6, 15 (GGA-Requirement-Register) |
| Replaced or carried by | GS11-staged, GS12-staged |
| Still open | none |
| What changes | Approval and revocation races are checked inside the release transaction: both users still authorised, listing active, applicant eligible. |
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
An approver has an active session and a prepared publish/accept transaction.
When
Revoke/downgrade membership before command authorisation; separately test a command already committed before revocation.
Then / oracle
Commands authorised after effective revocation fail without changes. Previously committed actions remain historical facts; future access is denied. Locking/version strategy supplies a documented authorisation/commit boundary, not a promise to recall completed work.
Evidence required
Controlled interleavings; membership version and commit audit; no post-boundary access.
Decision dependency (verbatim)
Q07: define in-flight transaction boundary and session invalidation semantics.
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.