Operations Console

This page is intentionally hands-on. Everything below runs on mock data so visitors can click a realistic mission map, switch internal hubs, open replay steps, and move scenario controls without needing a live backend.

Interactive operations console

Use a realistic 2D mission view instead of reading static product copy

Click a theater, switch hubs, inspect a replay chain, and push scenario sliders. This is still safe mock data, but the interaction model now mirrors the actual product much more closely.

Map drilldownHub switchingReplay reviewScenario controls

Visible layers

Operator pathEnergy -> shipping -> inflation

Decision window24-72h

Selected region

Hormuz

Shipping, insurance, and energy channels are converging around a chokepoint narrative. This mock region behaves like a live command view with route stress and country-pair tension.

Critical

TheaterMiddle East

Primary exposureOil / shipping / airlines

Signal mixNews 42 · AIS 7 · Rates 5

Country relations

Iran -> US88

Military and shipping channels are tightly coupled.

Iran -> Saudi Arabia67

Energy market signaling dominates direct cross-border risk.

Iran -> India54

Import exposure rises faster than direct security exposure.

Regional guidance

• Watch oil-linked ETFs and airline pressure paths before chasing broad risk-off.
• Use shipping and insurance chatter as confirmation, not first trigger.
• Operator review should separate physical closure risk from narrative escalation.

Recent mock events

Clustered strike chatter lifts marine insurance quotes.

Carrier rerouting headlines push freight and bunker sensitivity.

Gulf infrastructure mentions widen inflation-shock posture.

Replay and scenario workbench

The console above focuses on the operator surface. The workbench below focuses on historical replay, storage lifecycle, and scenario comparison with mock datasets that mirror the real replay stack.

Mock Replay Studio

Scenario and backtest workbench

This public demo uses synthetic point-in-time data shaped like the real replay stack. You can switch datasets, compare scenarios, and inspect how storage, evaluation, and operator posture move together.

mock datahistorical replayscenario console

Scenario

Middle East energy shock

Escalation lifts oil and shipping stress while safe-haven positioning turns defensive.

Defensive bias

Frames184

Idea cards7

Hit rate63%

CAGR+11.8%

Replay curve

ACLED · conflict events · 91% coverage

2025-10 -> 2026-03-6.4%

Input datasets

ACLED Middle EastACLED

conflict events · 91% coverage

Conflict and protest events anchor the regime shift signal.

GDELT chokepoint pulseGDELT

news / document stream · 78% coverage

News burst intensity confirms narrative acceleration around shipping routes.

Oil and hedge basketYahoo / FRED

price series · 96% coverage

USO, XLE, GLD, and TLT provide tradable exit points for the replay.

Decision posture

USO / XLE defensive carryWatch / deploy small

High conviction only when shipping stress and crude momentum confirm together.

GLD / TLT hedge sleeveDeploy

Macro overlay prioritizes capital protection over fresh cyclic exposure.

Scenario timeline

T-72hConflict burst enters hot cache

ACLED and news spikes land in Redis and feed the current snapshot.

T-24hReplay frame enriched

Transmission edges and hedge bias are recorded in the replay frame.

T+48hForward return closes

Max-hold fallback closes the position if no earlier clean exit appears.

Data lifecycle

HotRedis

Live conflict/news payloads stay in Redis with short TTL and schema checks.

WarmPostgreSQL

Replay frames and run summaries persist into PostgreSQL for operator review.

ColdParquet / R2

Parquet snapshots archive the scenario window for later point-in-time reproduction.

What this demonstrates

• 2D regional map with clickable hotspots and layer toggles
• country relations, regional guidance, and recent event cards
• hub switching across analysis, Codex, ontology, backtest, and resource views
• replay steps and scenario controls that change the same region's posture
• mock historical backtests over ACLED, GDELT, FRED, and market baskets
• hot / warm / cold storage flow that matches the current retention architecture

Limits

• mock data only
• no external APIs
• no private feeds, secrets, or service endpoints