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.

GS24 · Outcomes: company-confirmed and partner-reported stay distinct

Field	Value
Status	Not executed
Type	Balanced software (new in the GGA baseline)
Source	Blueprint pp. 2, 6, 8, 16, 19 (GGA-Requirement-Register); client-supplied draft, not accepted
Gate	GA07, GA12
Blueprint delivery stage	Stage 3 Complete the service loop (p. 19)
Build step	09 (primary; tests first)
Replaces or carries	DG06, DG13, DG14, DG15, DG16, T20
Decisions	—

Given

An introduction with an owner-reported and a company-reported outcome that differ. Follow-up prompts are due.

When

Record both; try to confirm value as a non-owner; try to create an invoice from the partner-reported outcome; let the 14-day and 45-day prompts run; close the introduction.

Then / oracle

Outcomes belong to the reporting company; only its authorised owner confirms its own value. Partner-reported and company-confirmed outcomes are kept apart and a partner-reported deal cannot trigger an invoice. States include introduced, discussion held, pilot, deal, no fit and no response; an introduction is not a completed deal. Prompts ask about progress, not assumed success, and stop after closure or opt-out. Registrations and pitches are not counted as realised value in pilot metrics.

Evidence required

Outcome rows by reporter; prompt jobs by cycle; metric definition source and window recorded.

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.