Approvals are events, with deadlines and an escalation path #1985
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: sam/archie#1985
Reference in new issue
Block a user
An approval request is an event out and the answer is an event in, whatever the channel or approver.
Done when: each of those behaviours is shown in the demo or the off-script checks.
Spec: section 6, decision tree 8.4, R27.
Landed in
4b1ae4bab,28733c852,dabe0b4f7,4bc0d5434and on staging (migration 00030). Each escalation step is a person with its own deadline (settings API and dashboard); the path skips people without authority for escalate-level actions; the run walks it with durable waits, and on final expiry runs nothing, withdraws a change request and reports. A re-judgement that is worse, or whose target or effect changed, discards the approval and asks again (up to 2 times); counting toward N happens only for an approval that still stands at run time. Change requests are routed by #1989's rules (Decision.ChangeRequest); with no change-request connector they go to the channels. Denied actions were already never re-proposed. Left: one approval covering a sequence, judged up front; reports and escalation notices go to every channel because deliveries has no per-person addressing; target-change detection sees only what the connector's Resolve reports.