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.
Q10 · Action visibility and overdue semantics
| Field | Value |
|---|---|
| Status | Pending GGA decision (recorded in 1.3 as “Pending DG decision”) |
| 1.3 to GGA disposition | Reframed |
| Responsible role to confirm (recommendation) | GGA product owner |
| Needed before | Before T29–T32 |
| Named owner | [ ] |
| Due date | [ ] |
| GGA approver / decision date / chosen rule | [ ] |
What the GGA documents say
Eligibility and due dates are computed at request time from UTC timestamps and shown in the user’s timezone; profile freshness replaces overdue actions as the main ‘overdue’ concept (pp. 7, 13). Next actions have no GGA feedback.
Source class: client-supplied design proposal or proposed default unless stated; GGA acceptance is not recorded. See GGA-Requirement-Register.
Rule or question as proposed in 1.3 (kept as history)
Use date-only due date in company business timezone, overdue after that day ends; confirm cross-party visibility and hold behavior.
Still open
Whether assigned next actions exist at all and their visibility; the date-only business-timezone rule for them stays a Proposed carry-forward.
Scenarios that depend on this decision (1.3 IDs, unchanged)
T29, T30, T31. Their dispositions are set in work package R4.
Related
GL03-staged, GQ04-staged. Index: Decision-Index.
A suggested default is a recommendation, not an approval. Record any actual decision with: ID · chosen rule · amendment to architecture and acceptance · GGA approver · decision date · affected test IDs · implementation owner.