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.
GS07 · Profile versions, attestation and stale-draft protection
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software (new in the GGA baseline) |
| Source | Blueprint pp. 4, 13, 14, 15 (GGA-Requirement-Register); client-supplied draft, not accepted |
| Gate | GA02, GA06 |
| Blueprint delivery stage | Stage 2 Foundation and publishing (p. 19) |
| Build step | 02 (primary; tests first) |
| Replaces or carries | T14, T15 |
| Decisions | — |
Given
A company has a confirmed profile version and an older draft open in a second browser tab. Business content is edited by a colleague.
When
Attest a newer version; save the older draft with its stale expected_version; edit business content and use the new version before confirming.
Then / oracle
Attestation, due date and audit event commit together. The older draft cannot overwrite the newer confirmed profile (409). Editing business content creates a new version that is not used until confirmed. Profile versions keep the confirming user, source and timestamps. One active attested version is retained.
Evidence required
Version rows, audit rows and response codes; transaction boundary shown by forcing a failure between the writes.
Decision dependency
None. The rule is stated in the Blueprint page cited above.
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.