Regime Shift Detector
Label the current market state so users know whether they are in trend extension, compression, conflict, or de-risk mode.
The live decision read
Regime Shift Detector converts agreement, direction, and realized move context into a simple market-state layer. It should function like a decision compass that sits above forecasts and reports.
Use the current commodity snapshot to decide whether the watchlist exposure needs research review.
A fresh price reversal, model disagreement, or catalyst miss would move this workflow route back to watch-only.
State confusion destroys decisions
When markets get noisy, users misread whether they are looking at continuation, reversal, or noise. A clean regime label reduces that confusion dramatically.
Turn noisy context into a state machine
Regime Shift Detector converts agreement, direction, and realized move context into a simple market-state layer. It should function like a decision compass that sits above forecasts and reports.
Preview the module on a live commodity
This workspace uses the current CommodityNode data stack and your saved workflow context so each product page behaves like a live decision-support surface instead of static brochure copy.
State vector → scenario candidates → replay evidence → review signal
Watch the active commodity move through a visible research workflow: state pressure enters the model, scenario candidates compete, replay evidence pushes back, and the review signal resolves in the center.
Current scenario snapshot ready
The decision console opens with the latest verified scenario signal, confidence, and baseline comparison, then refreshes when live model data is available.
How reliable is this scenario signal right now?
Freshness, stability, guardrails, and policy readiness are visible before a team uses the signal in a decision-support workflow.
What state is the model seeing right now?
Expose the live scenario context, state pressure, profile governance, and baseline comparison in one board so the user can audit the setup before deeper review.
See policy pressure moving across the action space
This field turns scenario-response probabilities into a living motion surface so the model feels like an active decision-support engine instead of a static table.
How does the scenario response compare with baseline policies?
Show hold, offline, PPO bootstrap, and Neural PPO side-by-side so the user can see whether the workflow route is actually better than the current baseline.
| Policy | Action | Confidence | Replay reward | Replay uplift | Walk uplift | Verdict |
|---|
Which policy survives across the full commodity basket?
Rank the active policies on the same five-commodity slate, then show the weakest commodity explicitly so the workflow route is backed by evidence instead of average-case optimism.
What is driving the current action?
Explain the strongest positive and negative drivers, then ground the workflow route with simple reason codes and comparable historical states.
What would flip this decision?
Explore how event risk, volatility, agreement, disagreement, and trend strength change the workflow route before a user commits to action.
What changed, and when?
Keep a timeline of workflow route events, profile selection changes, alerts, and replay evidence so users can audit the workflow route path instead of trusting a static score.
Operational readiness for this module
Latest decision snapshot available.
Fallback copy keeps the surface useful while live model data refreshes.
Open the linked workflow for the next decision step.
How users should read it
- Current regime badge
- State history strip
- Volatility / agreement quadrant
- Recommended play style per regime
What this helps decide
- Simple and sticky.
- Easy to understand and hard to replicate casually.
- Great for repeat daily check-ins and alerts.
Data required
- Live move
- Forecast direction
- Agreement score
- Volatility / shock context
What Pro adds to the workflow
- Free: current regime badge
- Pro: state history and regime logic
- Desk: saved regime alerts across commodities
Choose the right access level for Regime Shift Detector
Regime labeling monetizes well because it removes ambiguity when users need to know whether to trend-follow, hedge, or wait.
Current regime badge and a plain-language description of why it matters.
Live regime transitions, state labels, and decision notes.
Saved regime history, book routing, and handoff notes for teams.
State feeds, internal integrations, and multi-commodity monitoring across desks.
Quality standards for this module
- Keep regime labels simple enough to remember.
- Always pair the state with “what this means” guidance.
- Avoid pseudo-scientific jargon.