Auto-generated. This article is rebuilt from app/signals/config/signal_definitions.json by scripts/build_signals_kb.py. Edit the registry entry and re-run the script — do not edit this file directly.

Hormuz strait status

What it is

Hormuz strait status — registry key hormuz_strait_status.

Categorical status from hormuzstraitmonitor.com /api/dashboard (OPEN/RESTRICTED/CLOSED). Persisted to drive the dashboard card and history-aware change detection; no scoring contribution.

Data-pyramid tier

T4 — Regime / state. This metric sits at the regime / state layer of the platform’s six-tier data pyramid (T0 raw inputs → T5 actionable read). The tier reflects how far the value is from a raw measurement — not how strongly it is validated. Abstraction and validation are separate axes: a higher tier is not a claim of stronger evidence.

Horizon & validation

No validated skill horizon is on file for this metric — read it as context / a data carrier, not a validated edge. Stamps are added only when a gated research verdict lands.

Source

Source module: news
Data source: ad_hoc

Fetched directly from app/sources/news.py; see source code for the upstream API call and any provider-specific handling.

How it’s computed

Fetched directly from the news source; see app/sources/news.py for the upstream API call.

Where it surfaces

• API field: signals.hormuz_strait_status on GET /api/v1/signals/latest
• Surface: daily_signals row (daily-cadence persistence)

Health-score / alignment role

Data carrier — no implication, no health-score contribution.

Persisted for downstream consumers (sparklines, base-rate matcher, calibration substrate) but does not classify into BULLISH / NEUTRAL / BEARISH and does not contribute to the 0-100 health score.

Release cadence

• Publishes: intraday

Hormuz Strait Monitor publishes updates throughout the day.

See also

• /kb/api/get-signals-latest — API endpoint that serves this field.