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 status days ago

What it is

Hormuz status days ago — registry key hormuz_status_days_ago.

Derived integer days since status_since_date. Snapshotted per row so the card doesn’t recompute on every render.

Data-pyramid tier

T0 — Raw input. This metric sits at the raw input 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: computed

Derived metric — produced inside the platform (app/sources/news.py or equivalent) rather than fetched as a raw upstream value. See the How it's computed section below for the formula.

How it’s computed

No calculation_formula in registry for this derived metric. See the producer (app/sources/news.py) for the implementation.

Where it surfaces

• API field: signals.hormuz_status_days_ago 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

See also

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