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.
T18 · One active EOI survives duplicate submit and retry
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | API · database · race injection |
| Priority | P0 |
| Gates | A02, A08 |
| Build step | Step-06-Questions-Interest-Discussions-Actions |
| Decisions | Q05, Q07 |
Given
Two B users submit against the same opportunity and the client may lose a successful response.
When
Race submissions; retry key/payload after lost response and after access removal; reuse key with changed payload; try a separately authorised reopened attempt.
Then / oracle
One active EOI per B/opportunity. Scope idempotency to actor, command and attempt/generation plus key and payload hash. Check current authority before replay; never replay protected data to revoked actor. Same authorised request returns original result; changed payload fails. A permitted reopen uses new attempt/key, never old acceptance.
Evidence required
Database uniqueness; idempotency request hash/result; event-recipient uniqueness.
Decision dependency (verbatim)
Q05/Q07: active states, key retention and whether reopen/resubmit exists. No automatic resubmission is approved.
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.