Approvals and schedules

Outcome

You can identify what an approval must bind and why a schedule creates an ordinary budgeted run.

Prerequisites

Read the execution and state model.

Steps

1. Require an approval to show actor, exact action, normalized arguments, target, data exposure, cost, policy version, attempt generation, and expiry.
2. Resolve it through a durable product command, not a transient runtime prompt.
3. Treat expiry and denial as terminal decisions for that exact request.
4. Treat a schedule invocation as an ordinary run with explicit overlap and budget policy.

Approvals and schedules are not active in Slice 0. Their pages state the contract that later UI and workflow slices must prove; they are not instructions to bypass the missing capability.

Verify

A changed argument hash or generation requires a new approval. A schedule cannot bypass a hard budget, tenant boundary, or cancellation policy.

Recover

If an approval outcome is ambiguous, keep work paused and reconcile the durable request before any side effect. If a scheduled invocation overlaps unexpectedly, pause future starts and preserve the ordinary run for inspection.

Next task

Understand execution and state.