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.
T29 · Next-action creation and completion are participant scoped
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | API · E2E |
| Priority | P1 |
| Gates | A03, A04, A07 |
| Build step | Step-06-Questions-Interest-Discussions-Actions |
| Decisions | Q02, Q10 |
Given
A-B discussion exists; an entitled A user assigns an action within A. C and removed A members are not eligible.
When
Create/complete the action; attempt foreign-company, unassigned or removed assignees and viewer edits.
Then / oracle
Only active entitled assignees and actors succeed. Cross-company assignment is not silently granted. Completion is idempotent and removes overdue/pending status as defined. No implicit contract or payment state is created.
Evidence required
Assignment FK/policy checks; action history; participant list and pending-view assertions.
Decision dependency (verbatim)
Q02/Q10: which party can see/complete each action; cross-party assignment disabled unless separately agreed.
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.