Status. Proposed design only. Nothing in this vault is GGA client approval. The GGA client documents are supplied drafts: see GGA-Source-Digest. No application, service or test has been executed; every scenario is Not executed. Delivery fees and dates are open.
DG13 · Stalled work is not a DG surveillance trigger
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Manual DG service |
| Layer / kind | Manual + Balanced boundary |
| Priority | — |
| Gates | S03, S04 |
| Build step | 07 (GGA order; the 1.3 step is history) |
| Decisions | Q14, Q15 |
Disposition under GGA
| Field | Value |
|---|---|
| Disposition | Reframed |
| GGA basis | Blueprint p. 16 (GGA-Requirement-Register) |
| Replaced or carried by | GS06-staged, GS24-staged |
| Still open | none |
| What changes | Stalled-work help becomes outcome prompts at 14 and 45 days that stop on closure or opt-out. Prompts ask about progress, not assumed success. |
The 1.3 text below is kept verbatim as history. Where the disposition is Reframed, Superseded or Parked it is not the GGA oracle; use the replacing scenario. A Parked scenario has no GGA feedback and stays a Proposed carry-forward. The status stays Not executed. Register: Scenario-Dispositions.
Given
B has a private overdue action; A requests pressure on B. DG has no approved named overdue view.
When
Offer requested own-material office hours and process opt-out/stop-contact instruction.
Then / oracle
No named outreach from private overdue state; no ranking penalty or deadline pressure. Requester can approve a neutral invitation, subject to recipient contact permission. Stop-contact suppresses further relevant outreach; existing product action remains company-scoped.
Evidence required
Request/opt-out record, safe message and absence of DG query/join; T30/T31 access checks.
Decision dependency (verbatim)
Q14/Q15: manual cadence/close rule; named proactive product queue not included.
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.