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.
GS28 · Matching shows reasons and uses eligible companies and live offers only
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software (new in the GGA baseline) |
| Source | Blueprint pp. 7, 10 (GGA-Requirement-Register); client-supplied draft, not accepted |
| Gate | GA04 |
| Blueprint delivery stage | Stage 3 Complete the service loop (p. 19) |
| Build step | 05 (primary; tests first) |
| Replaces or carries | DG03, DG05, T06, T07 |
| Decisions | — |
Given
Companies with differing country, sector, offer and need, partner type, timing and owner-defined mandatory criteria. Published, expired and paused listings. A paid and an unpaid company.
When
Request suggested opportunities for each company.
Then / oracle
Only eligible companies are matched, and only to published, unexpired offers. Filtering by audience and status happens before ranking, counts and pagination. Each suggestion shows reasons and gaps; a missing fact is a gap, not a contradiction. A score is never described as a verified probability of success. Payment status does not influence ranking. SQL filtering is enough; no dedicated search infrastructure is assumed.
Evidence required
Suggestion output with reasons per case; counts equal visible items; ranking unchanged when payment status is toggled.
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.