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.
GS19 · AI drafts and assistance boundaries
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software (new in the GGA baseline) |
| Source | Blueprint pp. 4, 7, 11, 16 (GGA-Requirement-Register); client-supplied draft, not accepted |
| Gate | GA10 |
| Blueprint delivery stage | Stage 3 Complete the service loop (p. 19) |
| Build step | 12 (primary; tests first) |
| Replaces or carries | DG27, DG29 |
| Decisions | GL07-staged |
Given
An AI adapter is enabled in one run and absent in another. A draft summary is produced from permitted data.
When
Generate a draft; try to publish it; try to let it change eligibility, publish a listing, share contacts, send outreach or approve a fee; remove the adapter and save a profile.
Then / oracle
AI drafts are stored separately and stay unpublished until the company or publisher approves. AI cannot alter eligibility, publish, share contacts, send unsolicited outreach, approve fees or decide contribution status. A bot may assist entry but cannot certify or silently change facts. The core journey, including saving a profile, works without any AI or email provider.
Evidence required
State of draft versus published record; refusal per forbidden action; profile save with the adapter off.
Decision dependency
- GL07-staged: Whether an AI adapter is built at all is a launch decision; the matching and assistance features stay deferred in the first release (see GS25)
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.