Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
T05 · Publish an approved opportunity and discover it
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | E2E · API |
| Priority | P1 |
| Gates | A01, A04 |
| Build step | Step-04-Opportunities-Versions-Approvals |
| Decisions | Q02 |
Given
A approver has a complete assigned draft; B and C are approved members.
When
Publish the exact approved version; B searches by supported contribution and geography filters.
Then / oracle
One immutable version becomes live. B sees the permitted named opportunity with approved content and owner; drafts and private engagement fields are absent. Publication is not dependent on A having any partners.
Evidence required
Published version ID; UI/API response; indexed fields; no draft or private-canary values.
Decision dependency (verbatim)
Q02: approval binding; taxonomy and required essentials confirmed by DG.
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.