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.
Acceptance gates A01–A11 — Balanced treatment
Source: proposal p. 14 and architecture rev 3 p. 10. “Scoped” means a written amendment naming what is tested and what is unavailable; it is never presented as an unchanged pass.
| Gate | Balanced pass condition / boundary |
|---|---|
| A01 publish/find | Approved publication appears in permitted search and a supported rule-based recommendation. No AI or 80% matching-quality gate. |
| A02 respond without posting | A company without an opportunity asks a private question and submits meaningful interest, using the approved contributor workflow where required. |
| A03 independent discussions | At least three companies prove separate respondent threads; neither respondent can see the other; declining one leaves the opportunity open. |
| A04 delegated approval | Contributor prepares, approver publishes/submits, viewer cannot mutate; assignment/reassignment and sensitive actions audited. |
| A05 version changes | Material revision reviewed; prior approved content stays live; old interest retains its version; affected recommendations refresh. |
| A06 scoped revocation | UI, API, search, links, worker and email outputs enforce current access. Company-to-company exclusion and multi-company switching are unavailable, not recorded as passed. |
| A07 scoped lifecycle | Pause blocks new interest; existing discussion continues; approvals, assigned actions and discussion status work. Full expiry/reconfirmation and reported outcomes are deferred. |
| A08 scoped failure | Repeated submit/accept causes no duplicate record; worker retry, timeout reconciliation and failed-job recovery evidenced. No AI-outage test is claimed. |
| A09 scoped privacy | Named approved-member audience, assignment permissions and safe notifications enforced. Selected-company audience, exclusions and hidden identity deferred. |
| A10 scoped readiness | Load/recovery targets are agreed first (D10 / Q09); the gate stays unverified until tested. Then demonstrate secured credentials, restore, worker/mail evidence, runbook and named support ownership. |
| A11 language | Japanese translation excluded, not passed. English UI and immediate email policy under D07 have a proposed Step 11 A11-Language-and-Email-Checklist; coverage remains unverified and the applicable annex awaits DG confirmation. |
Release gate: no unresolved critical/high security defects or blocking functional defects; lower-severity accepted defects have an owner and date. DG signs off UAT; deployment needs separate written launch approval; defect-correction and re-test terms are proposed under D09. Payment follows software acceptance, never partnership outcomes (Delivery-Options-Comparison).
Scenario traceability: Traceability-Matrix.