Approvals are events, with deadlines and an escalation path #1985

Open
opened 2026-11-14 14:42:48 +00:00 by sam · 1 comment
Owner

An approval request is an event out and the answer is an event in, whatever the channel or approver.

  • Deterministic change-request rules, evaluated after the guards, decide which approvals go through a change request; all others go through the approver's channels.
  • Every escalation step has its own deadline, set per organisation; the path never drops below the authority the level requires. When it runs out, nothing is acted on, any open change request is withdrawn, and a report is sent. Expiry doesn't tighten the class.
  • An approval binds to the exact actions shown and can cover a sequence, judged up front; each action is judged again before it runs and waits for a new approval if its verdict got worse.
  • If something else changes the target, the approval is discarded, a new request goes out, and the discarded approval doesn't count towards N.
  • A denied action is never proposed again in the same run.

Done when: each of those behaviours is shown in the demo or the off-script checks.

Spec: section 6, decision tree 8.4, R27.

An approval request is an event out and the answer is an event in, whatever the channel or approver. - Deterministic change-request rules, evaluated after the guards, decide which approvals go through a change request; all others go through the approver's channels. - Every escalation step has its own deadline, set per organisation; the path never drops below the authority the level requires. When it runs out, nothing is acted on, any open change request is withdrawn, and a report is sent. Expiry doesn't tighten the class. - An approval binds to the exact actions shown and can cover a sequence, judged up front; each action is judged again before it runs and waits for a new approval if its verdict got worse. - If something else changes the target, the approval is discarded, a new request goes out, and the discarded approval doesn't count towards N. - A denied action is never proposed again in the same run. Done when: each of those behaviours is shown in the demo or the off-script checks. Spec: section 6, decision tree 8.4, R27.
sam added the featurehigh labels 2026-11-14 14:42:48 +00:00
sam added a new dependency 2026-11-14 14:42:59 +00:00
Author
Owner

Landed in 4b1ae4bab, 28733c852, dabe0b4f7, 4bc0d5434 and 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.

Landed in 4b1ae4bab, 28733c852, dabe0b4f7, 4bc0d5434 and 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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1985