> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bossmode.ing/llms.txt
> Use this file to discover all available pages before exploring further.

# Standing Orders

> Standing orders are the rules the consigliere follows when the boss is away. Define them once. They govern every autonomous move.

## 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

```bash theme={null}
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

```bash theme={null}
curl -sH "x-bossmode-token: $BOSSMODE_API_TOKEN" \
  https://bossmode.ing/api/pro/standing-orders | jq
```

### Delete a standing order

```bash theme={null}
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:

<AccordionGroup>
  <Accordion title="Revenue triggers">
    ```
    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.
    ```
  </Accordion>

  <Accordion title="Content and offers">
    ```
    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.
    ```
  </Accordion>

  <Accordion title="Spend and cost">
    ```
    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.
    ```
  </Accordion>

  <Accordion title="Communication">
    ```
    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.
    ```
  </Accordion>
</AccordionGroup>

## Standing order fields

| Field              | Type                              | Description                                 |
| ------------------ | --------------------------------- | ------------------------------------------- |
| `order`            | string                            | The policy, in plain English                |
| `priority`         | `"high"` \| `"medium"` \| `"low"` | Determines escalation urgency               |
| `scope`            | string\[]                         | Which engine scopes this order governs      |
| `requiresApproval` | boolean                           | Whether violations trigger an approval gate |
| `expiresAt`        | ISO 8601 date                     | Optional expiration                         |

## Scope values

| Scope             | Description                              |
| ----------------- | ---------------------------------------- |
| `pricing_move`    | Any change to pricing or offer structure |
| `offer_move`      | New offers, discounts, bundles           |
| `content_publish` | Publishing content to audiences          |
| `email_send`      | Sending email to any list                |
| `spend_change`    | Any cost or ad spend decision            |
| `client_comms`    | Communication with paying clients        |
| `data_export`     | Exporting 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

<CardGroup cols={2}>
  <Card title="Kill switch" icon="stop" href="/governance/kill-switch">
    How to halt all autonomous operations instantly.
  </Card>

  <Card title="Approval gates" icon="check-circle" href="/governance/approval-gates">
    How the approval queue works and how to configure it.
  </Card>
</CardGroup>