Momentum check
Example- Purpose
- Confirm whether early strength holds through the session
- Leaves when
- Move fades below its 30-step start level
- Review
- Every session
Monitoring workspace
Group what you watch, write alert rules you can explain, replay a session and keep a journal of what happened and why it mattered.
SYN-12 · moves ≥ 1.2% over 10 stepswarning · cooldown 25 stepsSYN-04 · volume ≥ 2.4× its 20-step averageinfo · cooldown 30 stepsSYN-21 · regime changesinfo · cooldown 40 stepsSYN-12 · volatility ≥ 0.45% over 15 stepscritical · cooldown 60 stepsEvents from the demo session appear here as rules fire.
Every value and event above is generated from a synthetic, fixed-seed session. Nothing here is live market data.
How it is used
The workspace follows the way careful monitoring actually happens: decide what to watch, decide what matters, observe, then review.
Each list has a purpose, an exit condition and a review cadence — not just tickers.
Thresholds, windows, cooldowns and severity, checked against a demo session before you rely on them.
Run the demo session, pause it, and see which rules fire and in which order.
Automatic events and your own notes on one timeline, ready to export.
Watchlists
Lists with a stated purpose stay small and stay useful. These examples use the synthetic instrument universe.
Alert Rules
Change the threshold, window or cooldown and see immediately how often the rule would have fired in the demo session.
Notify me in-app when SYN-12 moves ≥ 0.5% over 5 steps; then stay quiet for 0 steps.
In the demo session
Demo replay109 firings in 240 steps
Noisy: at this rate alerts become background. Raise the threshold or add a cooldown.
Scenario Monitor
A scenario card states what you are watching for, what would invalidate it and what you would do. The workspace tracks the state; it never forecasts.
Example cards for the synthetic instrument SYN-12. States reflect the demo replay, not a forecast.
Session Journal
Rule firings are logged automatically. Your notes sit next to them, tagged as expectation, check, miss or decision.
Workspace setup
Watchlists, rules and journal are saved to your account and recomputed on the server when you save.
Every saved rule is dry-run on the demo session, so you know how often it fires before you rely on it.
Configuration as JSON, journal as CSV or Markdown. Delete everything from Settings.
FAQ
It is a monitoring workspace: watchlists, alert rules with thresholds and cooldowns, a demo session replay with in-app notifications, and a session journal.
Advanced users who watch several conditions at once and want structure instead of more alerts.
It helps. Rule conditions use standard terms (volatility, volume, levels); the Methodology page defines each one exactly.
The Monitoring Workspace: up to 10 watchlists and 30 rules, demo replay, in-app notifications, session journal and export.
No. Noctivex never connects to brokers or exchanges, holds no funds and places no orders.
No. Every price, volume and event comes from a synthetic session generated with fixed seeds and is labelled as a demo.
No. Notifications appear inside the app during a replay. No email, SMS, push or webhook alerts are sent.
No predictions. Rules are deterministic conditions you write; the workspace shows when they would fire on demo data.
Your email, your workspace configuration and journal, a session while you are signed in, and consent records.
In Settings: delete workspace data or your account. It takes effect immediately.
Access
Confirm your email and the workspace opens with a starter watchlist. No password, no payment details.