Skip to main content

What are standing orders?

Standing orders are policy rules you write once and the consigliere reads on every brief. They define:
  • What the consigliere is allowed to do without approval
  • What must escalate to you
  • Which scopes (pricing, offers, emails, content) require sign-off
  • Priority thresholds for escalation triggers
Without standing orders, the consigliere defaults to requiring approval for everything. With them, you can safely delegate bounded work.

The standing orders API

Create a standing order

List standing orders

Delete a standing order

Writing effective standing orders

Standing orders are plain English. The consigliere interprets them as policy. Write them like you’d brief a capable employee:

Standing order fields

Scope values

Standing orders in Claude Code

The consigliere reads standing orders on every call. You don’t need to pass them manually. When you call bossmode:get-context, the response includes all active orders under standingOrders.

The consigliere brief

Every morning, the consigliere compiles a brief that includes:
  1. Active standing orders (reviewed for any updates)
  2. Open approvals waiting on you
  3. Revenue signals from the last 24h
  4. Work packets queued for each capo
  5. Guardian state (any blocked moves)
The brief goes into the Daily Report. You read it. You make decisions. The consigliere executes.

Next

Kill switch

How to halt all autonomous operations instantly.

Approval gates

How the approval queue works and how to configure it.