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.
T11 · Messages require current authority and safe input
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | API · E2E |
| Priority | P0 |
| Gates | A03, A06, A09 |
| Build step | Step-06-Questions-Interest-Discussions-Actions |
| Decisions | Q02, Q09 |
Given
B has an assigned contributor, viewer and removed member; A-B is a permitted existing conversation.
When
Send/read via all roles; forge author/company fields; submit oversized or script-like text.
Then / oracle
Server derives sender and company, applies current participant plus role/assignment access, and validates agreed limits. Viewer/removed/unassigned writes fail; safe rendering does not execute input. No private body is placed in email/logs.
Evidence required
Stored author versus session; request boundary cases; sanitized UI output and log/payload scan.
Decision dependency (verbatim)
Q02/Q09: message length, rate and retention limits; no additional message-email event 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.