/ops and /ops/monitors show the live monitor health grid. Each monitor reports green (healthy), amber (degraded — usually a stale tick or recent errors), or red (failing).

When a monitor goes amber: check the error count and last-tick age. If errors are growing, file an incident in Discord #ops. If only stale, give it one more tick window before paging.

When a monitor goes red: page immediately. The /doctor slash command in Discord shows the same data with one more level of detail.

Pending applications surface at /ops/callers?status=pending. Read the pitch and the three recent samples — the samples are signal-shaped messages the applicant has posted in #alpha-channels.

Approve if: samples are well-structured, pitch is concrete (specific markets they watch, not 'I'm good at predictions'), Discord account is at least 30 days old. Reject otherwise.

Approval grants the verified caller role and writes an audit entry. The applicant can re-apply after a 30-day cooldown if rejected.

/ops/users finds a user by id, username, source, Telegram chat id, or wallet address. Rows distinguish Sage, SageFNF, and overlap so ops can tell which infrastructure surfaced the account.