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.
T30 · Daily view mirrors the underlying authorised records
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | API · E2E |
| Priority | P1 |
| Gates | A04, A07, A09 |
| Build step | Step-08-Daily-Tracking-Views |
| Decisions | Q10 |
Given
Fixture includes pending approvals, unanswered questions, interests awaiting action, completed and overdue assigned actions across A-B/A-C.
When
Open each authorised user’s daily list; update, reassign and complete underlying items.
Then / oracle
Each item has current owner, due date if set, status and an authorised decision link. Counts/list agree, completed items leave active lists, and no unassigned private engagement leaks through counts.
Evidence required
Exact expected item-ID sets per role; before/after count diffs and deep-link checks.
Decision dependency (verbatim)
Q10: definitions of unanswered, pending and on-hold inclusion.
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.