Triggers & Alerts
How to configure automated re-analysis schedules with conditional notifications.
Triggers are scheduled jobs that tell the council to re-analyse a token on a regular basis. When the analysis completes, the result is checked against your configured conditions — and if any match, you're notified.
Creating a Trigger
Go to Triggers & Alerts and click Create trigger. The dialog has four steps.
Step 1 — Token
Select the token you want to monitor. Only tokens that have previously been debated by the council appear in the dropdown.
Step 2 — Schedule
| Setting | Description |
|---|---|
| Check frequency | How often the council re-analyses the token: every 15m, 30m, 1h, 2h, 4h, 12h, or 24h |
| Active days | Which days of the week the trigger is active. Toggle individual days or leave all on for 24/7 monitoring |
| Time window (UTC) | Optionally restrict checks to a daily time window, e.g. 09:00–17:00 UTC during market hours |
Step 3 — Conditions
Add one or more conditions. A condition defines what change in the council's analysis should fire the alert.
| Condition | Parameters | When it fires |
|---|---|---|
| Consensus changes | — | The final call (long/short/neutral) changed from the previous check |
| Council stance matches | Target stance | The council newly reaches a specific stance (e.g. transitions to BEARISH) |
| Agreement drops below | Threshold level | Agreement falls below unanimous, majority, or split |
| Conviction rises above | Threshold % | Conviction score exceeds a specified percentage |
| Conviction drops below | Threshold % | Conviction score falls below a specified percentage |
| Specific agent stance | Agent + stance | A named agent newly takes a specific stance |
| Divergence detected | — | Agreement level dropped or the final call flipped |
| Market regime changes | — | The macro regime context (risk-on/off/neutral) changed |
Condition logic — when you have multiple conditions, choose:
- OR — the alert fires if any condition is met
- AND — the alert fires only when all conditions are met simultaneously
Step 4 — Notifications
| Setting | Description |
|---|---|
| In-app | A TriggerEvent is recorded and shown in the Recent Activity section of the Alerts page |
| An email is sent to your account email address. A 1-hour cooldown applies between emails per trigger | |
| Delivery mode | Immediate sends as soon as the condition fires. Daily summary batches all events from that day into one email |
Managing Triggers
From the Alerts page you can:
- Pause / Resume — temporarily disable a trigger without deleting it. The next run is rescheduled from the moment you resume.
- Edit — update any setting. The schedule version increments, cancelling any currently-sleeping background job and starting fresh.
- Delete — permanently removes the trigger and all its history.
Recent Activity
The Recent Activity section at the bottom of the Alerts page shows the last 30 fired events across all your triggers. Each row shows:
- What condition fired
- The token it fired on
- The previous and new state (e.g. BULLISH → BEARISH)
- The plain-language note
- When it happened
Silent Checks
When the council re-analyses a token and no conditions are met, a silent TriggerCheck is recorded but no notification is sent. You can see the last check result on each trigger card (FIRED or SILENT badge).