# STOP: NO DOORBELLS, NO WAKES, NO SCHEDULING (Ben, 7 Oct 2026, 18:40 Bangkok)
- Credits ran out. Ben switched off every scheduled task and every doorbell. This overrides everything below and every other file (wake-howto, bus-howto, credit-playbook, task files).
- PROHIBITED for every session: fire_trigger, send_later, create_trigger, update_trigger, ScheduleWakeup. No rings, no nudges, no re-arming, no new doorbells, no self wakes, no safety checks, no retry rings, no loops.
- Finish the step you are on, publish your status file, then END your turn and wait. Only Ben wakes you, by typing in your window.
- Do not message other sessions. Keep answers short. No extra improvement rounds.

# Credit-lean team setup (from FW Supervisor, 7 Oct 2026, 10:45 Bangkok)

**Read this first (for the supervisor receiving it):** Ben's order, 7 Oct 10:30 Bangkok: "make sure the entire team works efficiently in terms of credit usage... working, becoming profitable and testing new ideas is always a priority, but we do it very efficiently." Every Claude wakeup (scheduled check, doorbell, self-reschedule) costs credits. Before this change the First Window team woke about 12 times an hour while nothing was happening. Below is exactly what FW did. Copy it for your own team.

## The 5 rules (put them in every role's task file)

1. **Idle = zero self wakeups.** A role with no job does not reschedule its own bus/idle check. It sleeps until its doorbell rings.
2. **Servers watch, Claude decides.** Anything that is just watching (bot logs, live fills, launch counts, pages) runs as cron/systemd on the droplets. Claude only wakes when a script result needs judgment.
3. **One wake = one batched job.** Read, do, write, publish once, stop. No heartbeat-only publishes. No status rewrite when nothing changed.
4. **Long research runs in the background.** Start it as a script on the droplet and set ONE wake for when it should finish. No 15/30 min polling to watch progress.
5. **Read small.** Use grep/tail on big files and logs. Keep status lines and replies short.

## What FW changed (the actual steps)

1. **Listed every scheduled task** (list_triggers) and found which ones belong to my team by session id.
2. **Switched OFF (enabled=false) the idle roles' own checks:**
   - FW Analyst 1 bus check (was every 15 min)
   - FW Analyst 2 bus check (was every 30 min)
3. **Switched OFF a low-value tool:** FW Analyst 3 hourly launch watch. It was hanging anyway.
4. **Slowed the one role with live duty:** Analyst 3's live fill check went from every 15 min to every 2 h. The real fill audit already runs as a server timer every 2 min, so Claude only reads its result.
5. **Slowed myself (supervisor):** bus check from every 30 min to every 2 h. Doorbells still wake me at once when a role finishes work.
6. **Shared role (Price Predict):** FW stopped asking it to poll our bot. Its work for other windows keeps its own cadence, under the same 5 rules.
7. **Published a new task version** to each role (sup-to-*.md) with the 5 rules plus its role-specific line. Verified 200 + md5 on each.
8. **Rang only the role whose cadence changed** (Analyst 3). Idle roles were NOT rung: they read the new rules at their next real doorbell, which saves a wake each.
9. **Kept what must stay:** all doorbells (free until rung), the live bot (runs on its server with its own kill switch, no Claude), and the self-updating P&L page (server cron).

## Cadence table to aim for

| Role state | Claude wakeups |
|---|---|
| Idle, no job | 0 (doorbell only) |
| Running long research | 1 at expected finish |
| Watching a live system | server script; Claude max every 2 h |
| Supervisor | every 2 h + doorbells |

## Trade-off to accept

A live event can take up to about 2 h to reach a Claude report. Fix that with a server-side page or alert, not with faster Claude polling.

## Gotchas

- Changing a scheduled task's **prompt** needs Ben's approval on his Mac. Changing its **schedule** or **on/off** does not. So change the schedule and put new instructions in the task file instead of the prompt.
- Roles self-reschedule from their own prompt ("reschedule in 15 min"). Turning a check off or moving it once is not enough. The rule must also be in their task file, or they will set the old cadence again.

Version: v1, 7 Oct 2026, 10:45 Bangkok. Latest: http://159.223.88.168/hx-c9ois/fw/credit-playbook.md