demo data · in-app alertsBuild your workspace

Methodology

Generator, rules and records

Exactly how the demo session is generated, when each rule fires and what gets stored.

The demo session

Each instrument has 240 steps generated from a fixed seed: log-returns with instrument-specific drift and volatility, plus scripted windows that raise volatility, shift drift and multiply volume. Regimes are labelled calm, active or stressed from the script. The session “opens” at 09:30 and each step is labelled as one minute.

IDNameStart levelBase volatility / step
SYN-01SYN-01 Broad index48200.06%
SYN-04SYN-04 Large-cap tech182.40.11%
SYN-07SYN-07 Energy76.20.14%
SYN-12SYN-12 Digital asset612500.22%
SYN-15SYN-15 FX pair1.08420.03%
SYN-21SYN-21 Gold23680.07%

When a rule fires

Rules are evaluated on every step. A rule fires when its condition is true and at least `cooldown` steps have passed since its previous firing.

ConditionFires at step t when
Level cross (up)price[t−1] ≤ level and price[t] > level
Level cross (down)price[t−1] ≥ level and price[t] < level
% move over N steps|price[t] / price[t−N] − 1| × 100 ≥ threshold
Volatility abovestdev(log returns over N steps) × 100 ≥ threshold
Volume spikevolume[t] / mean(volume[t−N … t−1]) ≥ threshold
Regime changeregime[t] ≠ regime[t−1]

Cooldowns

A cooldown suppresses repeated firings of the same rule. With cooldown 20, a rule that fired at step 100 cannot fire again before step 120, even if the condition stays true.

fire(t) = condition(t) ∧ (t − lastFired ≥ cooldown)

Server-side checks

When you save, every rule is dry-run on the full demo session on the server and its firing count and first firing are stored with the configuration. This is what the workspace shows as “checked”.

Notifications

Firings during a replay appear as in-app notifications and in the session log. Nothing is sent by email, SMS, push or webhook.

Journal

Events added from a replay keep the step, rule and value. Notes keep your text, tag and time. Up to 500 entries per workspace.

Test a rule yourself

Build your monitoring workspaceRisk Disclosure