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.
T10 · Third respondent has a separate private conversation
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | E2E · API · security |
| Priority | P0 |
| Gates | A03, A09 |
| Build step | Step-06-Questions-Interest-Discussions-Actions |
| Decisions | Q08 |
Given
A-B and A-C contain distinct canary messages, EOI terms and next actions.
When
B and C exchange messages with A, then request each other’s IDs, lists, counts and links.
Then / oracle
A can work both authorised threads; B cannot read, infer or change C’s private engagement and vice versa. Shared public opportunity content remains visible. Neither respondent list exposes competitor identity/activity.
Evidence required
Canary absence across response bodies, counts, snippets, notifications and errors; positive counterparty evidence.
Decision dependency (verbatim)
Q08: DG metadata allowlist; private respondent counts are not public by default.
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.