Caller behaviour that smells off: signals that look like front-running (caller fires immediately after a big whale trade in the same direction), pump-and-dump patterns (multiple signals on a thin market within minutes), or clear coordination across accounts.

Signals with intentionally misleading thesis. A caller writing 'CPI prints 3.5%' when no such print is scheduled is gaming subscriber attention.

Account compromise — you signed in and your tier changed, or you see signals fired from your account that you didn't fire, or your Telegram link points at a chat you don't recognize.

Anything that feels like a security incident, however vague. Even a hunch is worth flagging; ops reviews every report.

Routine reports — DM @ops in the Sage Discord with the signal ID (or signals — multiple are fine), the caller's handle, and one sentence on why. Ops triages within a business day.

Urgent reports (account compromise, active manipulation) — DM any oracle or admin directly. The full oracle + admin roster is pinned in the #ops-public channel.

Email path — ops@sagefnf.com. Used when the Discord path is broken (your account is locked, etc.). Include your Discord user ID + the issue.

Triage. An oracle reads the report + cross-checks the signal IDs against the audit log + the caller's history. Usually clarifies within hours.

Investigation. If patterns hold, ops pulls the full audit row for every related action. Manipulation reports cross-reference whale-tape activity around the same time.

Outcome. Three possible: (1) no action — the report doesn't reproduce. (2) caller-side action — verified-caller role suspended pending review, signals from the period flagged in the leaderboard math. (3) account-side action (compromise reports) — session forced-revoked + the user is notified to re-sign-in + change Discord password.

You get a private DM with the outcome. Ops does NOT publicly name the caller or the reporter; the audit row records the action without exposing either side.

Don't call out a caller publicly in #alpha-channels or other Discord channels. If they're misbehaving, ops will handle it. If they're not, you've just shamed someone in public.

Don't try to short-circuit by 'investigating' on-chain yourself if you're not already deep in this — the Polymarket on-chain activity around any popular signal is messy + most of what looks like manipulation is normal market making.

Don't repeatedly file the same report. One submission lands in the queue + it's worked. Duplicates get auto-closed + you'll be asked to wait.