Status & monitoring

Dashboards

• Status site: trades.yourevenings.com/status.html — token-gated, public-share-able if needed.
• Refresh: 30s auto.
• Source of truth: monitoring cron aa4111a7-c9f2-460f-b8a9-1e1e37ec847b runs every 15 min.

What's monitored

Component	Check	Pass criterion
YE bridge	GET https://bridge.yourevenings.com/	not 000 or 5xx (404 OK)
Vapi assistant	API responds, credits > 0	response 200, balance > $5
Twilio account	API responds, balance > 0	response 200, balance > $5
Polly UK number	Vapi reports number bound	bound to assistant ID
Status site itself	self-check	200

Alert behaviour

• state-change-only. We don't alert on every poll — only when something flips colour.
• Vapi transient timeouts → reported as skipped (silent), not yellow. Eliminates flap noise.
• Bridge 404 → green (acceptable per HEARTBEAT.md).

Alert sinks

• Telegram → Matt's chat (5336018303)
• Cron failure-alert mode: announce

Heartbeats

Matt's main OpenClaw session runs heartbeats every 30 min:

• Reads /data/.openclaw/workspace/HEARTBEAT.md
• Runs curl https://bridge.yourevenings.com/
• Reply HEARTBEAT_OK if all green
• Trading is shut down — no trading checks run

When something goes red

1. Check the status site.
2. Check the failing component's dashboard (Vapi, Twilio, CF, bridge).
3. See Runbooks for component-specific recovery.
4. If you can't fix in 10 min, ping Matt.

What "skipped" means

A component check timed out or hit a transient network issue. Not a fail. If the next 15-min check is green, it was a blip. If two consecutive skippeds → investigate.