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.
T31 · Overdue is defined at a reproducible time boundary
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | Unit · API |
| Priority | P1 |
| Gates | A07 |
| Build step | Step-08-Daily-Tracking-Views |
| Decisions | Q10 |
Given
Controlled clock and chosen company business timezone; actions due yesterday, today, tomorrow, none and completed. Test a timezone with a clock-change boundary too.
When
Evaluate just before/at/after local due-day boundary and when different users view the same record.
Then / oracle
All views classify the same due-date value using the signed date/timezone rule. Completed/undated actions are not overdue. No browser-local guess changes the result. No overdue email escalation is emitted in Balanced.
Evidence required
Frozen-clock table with UTC instants and expected labels; persisted timezone and due semantics.
Decision dependency (verbatim)
Q10: recommended date-only due date in company business timezone, overdue after that local day ends; DG approval required.
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.