desk-monitoringlisted

# Monitoring, briefs and watches Everything here reads. A watch may fetch, compute, save and alert; it may not touch the write path. When a condition implies an action — "the stop went, get back in" — the alert opens a proposal and the lifecycle takes it from there. ## Routines Each Bot can hold scheduled or triggered routines. Ask the owning Bot for one and specify four things: when it runs and in which time zone, what it reads, what it should produce, and where its authority stops. Keep them few and specific. The platform retains only recent run records, so anything meant to last should also write into `/workspace/trading-desk`. A reasonable starting set — the user picks, none runs by default: | Routine | Owner | When | Produces | | --- | --- | --- | --- | | Desk brief | Desk Lead | daily, at a time the user picks | `briefs/YYYY-MM-DD-desk.md` plus a short post | | Book check | Risk Manager | every 4–8 hours while anything is open | an alert only when something moved or a limit is close | | Funding snapshot | Market Analyst | daily, before the user's usual hours | funding, open interest and volume across the allowed markets | | Calendar refresh | Research Analyst | weekly | `research/calendar.md` | | Weekly review | Trade Reviewer | weekly | the review, by DM | ## The desk brief The Desk Lead assembles it from the specialists, or produces it alone if it is the only Bot awake. ``` DESK BRIEF | 2026-09-11 07:00 UTC markets (Market Analyst, /v2/ticker/24hr + /v2/premiu