Skip to content

Delay windows

A delay window is the time a reviewed one-way Action waits before it runs, so someone can step in; if nobody does, it proceeds.

A delay window is the time a reviewed one-way Action waits before it runs. Anyone watching can step in while it waits; if nobody does, the Action proceeds.

A window is not an approval

Delay windowApproval
Opens whenA one-way Action passes review.An Action exceeds a Limit.
Needs a yesNo.Yes.
When time runs outThe Action runs.The Action ends canceled.
Shows up asA pending item in the inbox and the stream.A Task.

Approvals and the legal floor are the only gates. A window adds a chance to intervene and never waits for anyone.

Lengths and the clock

TierWindow
LowNone: the Action runs after review.
Medium1 business hour
High1 business day

The decision class of the Action's Verb sets its tier. Windows count business hours on the namespace's calendar, holidays included. A high-tier price change queued at 16:00 before a weekend runs at 16:00 on the next business day.

While it waits, the Action is pending with the reason awaitingTime. The window's Setting says when it closes, and any watcher may pause, redirect or cancel it until then.

JSON
{
  "$id": "https://api.sb/freightrates.dev/actions/action_7",
  "operation": "Offer.update",
  "status": "pending",
  "reason": "awaitingTime",
  "mode": "send",
  "by": "https://api.sb/freightrates.dev/agents/pricing"
}

Settings that only tighten

Windows are Settings held at the Studio, a Portfolio or a Startup, and they inherit down the tree. A child may lengthen a window or raise a Verb's class. It never shortens one or lowers a class.

A Mandate carries its own window for sends made in a person's name. An agent sending as its founder follows that window, or the Mandate's approval rule when it has one.

What never waits

Review runs before the window opens, never in place of it. Two-way, low-tier Actions run the moment review passes.

Stopping is always immediate. A guardrail stop, a brake, a pause and a revoked Mandate take effect at once, with no window of their own.

In practice

A Dataset API sells freight rates to buying agents. At 15:00 one afternoon, its Product Lead raises the per-call Price by 20 percent, a high-tier change. The founder's personal agent reads it that evening, finds nothing wrong, and the change runs at 15:00 the next business day.

The same afternoon, a $40 refund waits one business hour and goes out. Nobody approved either Action.