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.
T17 · EOI is meaningful and references what B reviewed
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | Unit · API · E2E |
| Priority | P1 |
| Gates | A02, A05 |
| Build step | Step-06-Questions-Interest-Discussions-Actions |
| Decisions | Q05, Q08 |
Given
B has no published opportunity; A’s live version V1 is visible. B prepares contribution, expected benefit/return, conditions and responsible contact.
When
Submit approved interest; omit required fields; try A-to-A self-interest; inspect verification immediately before/at/after DG-agreed evidence expiry.
Then / oracle
EOI references immutable V1 and B company; required omissions/self-interest fail without event. Before acceptance A sees only approved B profile and deliberately disclosed EOI fields/contact, never C terms. Verification shows evidence/last-check date and stale/non-current label under DG validity rule; no guaranteed status or automatic re-verification.
Evidence required
Required-field/visibility tests; version FK; verification age boundary and unknown evidence; safe event.
Decision dependency (verbatim)
Q05/Q08: exact profile/contact/EOI allowlist, conditions and verification validity/source. No hidden-field unlock at accept.
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.