desk-monitoring

# Monitoring, briefs and watches Monitoring is read-only. A watch may fetch, compute, save and alert. It may never send to the exchange. If a watch condition implies action ("stop got hit, re-enter"), the alert opens a proposal; the lifecycle does the rest. ## Grok Bot routines Each Bot can own routines (schedules or event triggers). Ask the owning Bot to create one with: schedule and time zone, input source, expected result, approval boundary. Keep routines few and specific; the app keeps only recent run records, so a routine that produces something durable should also write to `/workspace/trading-desk`. Recommended starting set (the user picks; none is on by default): | Routine | Owner | Schedule | Output | | --- | --- | --- | --- | | Desk brief | Desk Lead | once a day at the user's chosen time | `briefs/YYYY-MM-DD-desk.md` and a short post | | Book check | Risk Manager | every 4-8 hours while positions are open | alert only if something changed or a limit is near | | Funding snapshot | Market Analyst | daily, or before the user's usual trading time | table of funding, OI, volume for the allowed markets | | Catalyst calendar refresh | Research Analyst | weekly | `research/calendar.md` | | Weekly review | Trade Reviewer | weekly | review posted by DM | ## The desk brief Assembled by the Desk Lead from specialists' inputs, or generated by the Desk Lead directly if it is the only Bot awake: ``` DESK BRIEF | 2026-08-17 07:00 UTC | mainnet | account 0xabc...def markets ...