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

curl -sX POST https://bossmode.ing/api/pro/standing-orders \
  -H "x-bossmode-token: $BOSSMODE_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "order": "When inbound revenue from Stripe exceeds $5,000 in 24h, escalate to me before any pricing change.",
    "priority": "high",
    "scope": ["pricing_move", "offer_move"],
    "requiresApproval": true
  }'

​
List standing orders

curl -sH "x-bossmode-token: $BOSSMODE_API_TOKEN" \
  https://bossmode.ing/api/pro/standing-orders | jq

​
Delete a standing order

curl -sX DELETE https://bossmode.ing/api/pro/standing-orders/{order_id} \
  -H "x-bossmode-token: $BOSSMODE_API_TOKEN"

​
Writing effective standing orders

Standing orders are plain English. The consigliere interprets them as policy. Write them like you’d brief a capable employee: 
When any single transaction exceeds $2,000, log it and surface it in the morning report. Do not adjust pricing without explicit approval.

If daily revenue drops more than 50% from the 7-day average, escalate immediately — do not wait for the morning report.

Content targeting new audiences must be reviewed by me before publishing. Content for warm audiences (existing list) can go out without review.

Promotional offers over 20% discount require my approval. Standard nurture sequences can execute automatically.

No ad spend changes without approval. Log all cost events. Flag any unexpected charges over $100.

SaaS renewals under $50/month can auto-approve. Renewals over $50/month require review.

All client-facing communication goes through the approval queue. Internal planning notes can proceed automatically.

Do not email any address more than once in a 72-hour window without approval.

​
Standing order fields

FieldTypeDescription
orderstringThe policy, in plain English
priority"high" | "medium" | "low"Determines escalation urgency
scopestring[]Which engine scopes this order governs
requiresApprovalbooleanWhether violations trigger an approval gate
expiresAtISO 8601 dateOptional expiration

​
Scope values

ScopeDescription
pricing_moveAny change to pricing or offer structure
offer_moveNew offers, discounts, bundles
content_publishPublishing content to audiences
email_sendSending email to any list
spend_changeAny cost or ad spend decision
client_commsCommunication with paying clients
data_exportExporting lead or customer data

​
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.