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.
T04 · Reassignment moves work without duplicating it
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | API · database · E2E |
| Priority | P0 |
| Gates | A04, A06, A07 |
| Build step | Step-02-Identity-Membership-Roles |
| Decisions | Q02, Q07 |
Given
A question and action are assigned to active A1, who is on leave; A2 is eligible and A3 removed.
When
Admin reassigns to A2; attempt assignment to A3 or another company; race reassignment with a message.
Then / oracle
Leave alone does not revoke authority or detect absence. Authorised admin sees unanswered work and explicitly reassigns it. Record/history persist and pending lists move once. Foreign/removed assignment fails; A1 loses assignment-only access. No broadcast, absence detection or extra email event is promised.
Evidence required
Same conversation/action IDs; current permissions; audit and pending-list deltas.
Decision dependency (verbatim)
Q02/Q07: name unanswered-work owner and recipient/reassignment rule; no automatic fallback assumed.
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.