Market Intelligence Engine v3

Hanzo AI's multi-dimensional market-data analysis core — 8 analytical modules running across 31 pairs and 5 timeframes, from session timing to harmonic patterns, volume profiling, Wyckoff phase detection, and divergence scanning. The modules feed a Confluence Map that organizes related readings for structured review and supplies context to Operator Agent briefings.

What this page covers

  • What each of the 8 HMIE analysis modules does and how to use it
  • How to navigate pairs and timeframes effectively
  • How the Confluence Map synthesizes all modules into ranked setups
  • The workflow for using HMIE to compare educational market-data observations

What is HMIE v3?

The Hanzo Market Intelligence Engine (HMIE) version 3 is the analytical core of the platform. It runs 8 distinct analysis modules simultaneously across 31 supported forex, metals, indices, and commodity pairs — on 5 timeframes: 15-minute, 1-hour, 4-hour, Daily, and Weekly.

The key design principle of HMIE is confluence: no single model reading should be treated as a conclusion. The engine organizes where multiple analytical labels overlap at a similar level or time so learners can compare the source context and uncertainty.

The 8 Analysis Modules

  • Kill Zone Panel

    Session windows at 10:00 UTC (London-NY overlap) and 13:00 UTC (NY midday). Shows window status, session context, historical observations, and a model bias label (bullish/bearish/neutral) for review.

  • Divergence Engine

    Detects price-versus-momentum divergences across RSI, MACD, and Stochastic. Labels regular and hidden divergence as model classifications for comparison across monitored pairs.

  • Volume Profile

    Displays point of control (POC), value area high (VAH), value area low (VAL), and high-volume nodes (HVN) for each pair and timeframe. These are descriptive views of recent activity by price.

  • Harmonic Patterns

    Detects Gartley, Bat, Butterfly, Crab, Shark, and Cypher pattern candidates. Shows completion-zone geometry, PRZ (potential reversal zone) labels, Fibonacci levels, and historical reference fields.

  • Confluence Map

    Overlays readings from the other modules and groups price areas where multiple model labels overlap. Color coding indicates the displayed count; it does not establish independence or outcome probability.

  • 30-Day Timeline

    Displays recent signal history for the selected pair over 30 days, including follow-through observations, session labels, and comparisons with recent conditions. Historical records are retrospective.

  • AI Market Study Generator

    Synthesizes active module readings into a plain-English market-data summary with model bias labels, reference levels, and the analytical factors cited by the system. It is not a trade recommendation.

Monitored Pairs

HMIE v3 covers 31 pairs across supported forex, metals, indices, and commodities:

Asset ClassPairs covered
Forex MajorsEURUSD, GBPUSD, USDJPY, USDCHF, USDCAD, AUDUSD, NZDUSD
Forex MinorsEURGBP, EURJPY, GBPJPY, AUDJPY, EURAUD, GBPAUD, CADJPY, CHFJPY, EURCAD, GBPCAD, NZDJPY
CommoditiesXAUUSD (Gold), XAGUSD (Silver), WTI Crude Oil

Timeframes & Their Purpose

TimeframePrimary useBest for
15-minute (15m)Intraday scalping and entry precisionRefining entries on higher-TF setups
1-hour (1H)Session trading and kill zone entriesKill zone entries, Wyckoff events
4-hour (4H)Swing entries and daily biasHTF structure, harmonic completions
Daily (1D)Directional bias and major S/RKey levels, weekly range projection
Weekly (1W)Macro structure and institutional biasLong-term trend, major accumulation/distribution

Data Update Frequency & Freshness

Each HMIE module has its own update cadence. Understanding when data refreshes helps you know when to reload the dashboard for the most current view:

ModuleUpdate frequencyLast scan shown in UINotes
Kill Zone PanelReal-time (live clock)Live countdownBias updates every 30 min
Divergence EngineEvery 5 min (15m/1H), every 30 min (4H/D)Timestamp in module headerHistorical divergences don't update; new ones append
Volume ProfileEvery 4 hours (recalculates full POC/VAH/VAL)Date of last full recalculationIntraday changes visible on lower TFs more quickly
Harmonic PatternsEvery 15 min (checks for new completions on all TFs)Timestamp in feedPatterns don't repaint once detected
Confluence MapEvery 5 min (live composition of all other modules)Top-right timestampRefresh page if map seems stale — cache is 5 min max
30-Day TimelineDaily at 00:00 UTCDate column in timelineHistorical performance data; updates once per day
AI Market Context GeneratorGenerated fresh on each clickPer-generation timestampEach click produces a new educational analysis from current data

Pre-Session Briefing with HMIE

The most effective use of HMIE is a structured 10-minute pre-session briefing before the London-NY kill zone opens. This briefing gives you a clear picture of which pairs have the highest-quality setups for the session before any position is considered:

1. CONFLUENCE MAP — identify today's top 3 pairs
   → Open HMIE → Confluence Map tab
   → Filter: 4H + Daily timeframes only
   → Note any pair with orange (4+) or red (6+) confluences
   → Today's result: XAUUSD (6 confluences, red) ← primary
                     GBPUSD (4 confluences, orange) ← secondary
                     EURUSD (3 confluences, yellow) ← watch

2. DIRECTIONAL BIAS (for top pair: XAUUSD)
   → Kill Zone Panel: XAUUSD Session Bias = BULLISH
   → Wyckoff Gate 4H: Phase = Markup, WPS = 78, last event = LPS
   → AI Context Generator: "Bullish scenario noted for review near a historical reference zone"

3. KEY LEVELS FOR THE SESSION
   → Volume Profile POC: $2,295 | VAL: $2,278 | VAH: $2,314
   → Pattern Intelligence: 1H FVG at $2,289–$2,292 (unfilled)
   → Confluence at $2,289–$2,292: FVG + OB + VAL proximity = 4 factors

4. HYPOTHETICAL STUDY NOTES
   → Observe the modeled FVG near $2,291
   → Record $2,279 as an example invalidation assumption
   → Compare later prices with the example reference levels
   → Review the result after the session; no live action is implied

Recommended HMIE Workflow

  1. Review the Confluence Map

    Use the Confluence Map to compare where several model readings overlap across a watchlist. Colors and counts describe model state; they do not rank opportunities.

  2. Compare timeframe labels

    Record whether a model classification appears on one or several timeframes, then compare it with the underlying charts and later data.

  3. Review session context

    Use the Kill Zone Panel to understand which configured session window is active and how the platform labels that context.

  4. Read the AI rationale

    Read the generated rationale as educational model output and verify its inputs independently. It may be incomplete or inaccurate.

  5. Cross-reference Volume Profile

    Compare a modeled zone with POC and VAL/VAH reference levels without treating overlap as a probability estimate.

  6. Use study alerts

    Optionally set an Alert Intel rule to revisit a level for observation and later review.

Frequently asked questions

How often does HMIE data update?

Signal data is updated at different frequencies: 15m and 1H scans run every 5 minutes. 4H and Daily scans run every 30 minutes. Weekly data updates every 6 hours. The last scan time is shown in the top-right of the HMIE dashboard.

What is the difference between HMIE v2 and v3?

HMIE v3 upgrades the AI Market Context Generator to Hanzo AI's latest model, expands coverage to 31 supported pairs, and introduces the Confluence Map as a standalone module with a visual heat map.

How many pairs should I monitor in HMIE at once?

The number depends on your research question and capacity to review source data. Comparing fewer instruments may be more manageable for some workflows, while a broader scan may suit others. Neither watchlist size nor model ranking identifies a priority or predicts an outcome.

What is a 'confluence' exactly and how many is enough?

Confluence describes multiple analytical labels appearing in related contexts. For example, a Fibonacci retracement, volume-profile level, Wyckoff label, and order-block label can be compared as separate observations. There is no universal minimum count or quality threshold; overlap does not establish probability or suitability.