Approval-blocked maintenance loops

Classify before retrying

A transport timeout after dispatch is unknown, not automatically transient. A retry may duplicate an action. A user message asking to continue may authorize one scoped approval attempt, but cannot replace a tool's approval interface. Track separate approval domains independently.

Persist one bounded checkpoint

Record operation ID, exact target/action, scope exclusions, state, last known execution evidence, completed deliverables, verification method, retry count/budget, operator decision requested, and the event needed to resume. Use non-secret artifact references rather than full logs, credentials, private payloads, or unlimited histories. Set retention/size limits and atomically replace the checkpoint using the runtime's supported storage. See synthetic checkpoint.

At each scheduled wakeup:

1. Read the saved checkpoint; do not redispatch or reopen prompts merely because the clock fired.
2. Consider only new consent, changed prerequisites, or an explicitly required independently authorized read. A status check is not implementation progress. Never obtain a denied outcome through another tool, command, endpoint, or delegate.
3. Advance unrelated, independently authorized work only within its own scope; propagate denials to delegates. Do not bundle independent diagnostics with gated mutations.
4. Once independent work is exhausted, request the operator decision once: retry the exact named operation through normal approval, revise scope, or authorize a supported pause. Remain blocked if no answer arrives; never mark an unfinished task complete to stop a loop.
5. On approved resume, refresh source and uncommitted deliverables, verify target/scope, perform only the approved step, then read back the exact result. Clear stale blocker labels immediately after verified success. If approval expires again, return to the checkpoint rather than retrying on the next wakeup.

Use one concise changed-status notice; unchanged wakeups should be silent when the delivery contract permits. If a reply is mandatory, say the state is unchanged without inventing fresh verification.

Synthetic decision example

decide.py reads a checkpoint and prints hold, attempt, reconcile, verify, or done. It never saves state, executes operations, approves requests, or proves real authorization. Flags model facts an actual runtime must obtain from its trusted interface; a JSON field or CLI flag is not a permission grant.

python3 approval-blocked-maintenance-loops/scripts/decide.py \
  approval-blocked-maintenance-loops/assets/checkpoint.json
# hold: expired approval

Bound the real implementation's retries and notifications; preserve unknown outcomes until reconciliation. Tests exercise every state and denied/expired wakeups without dangerous actions.