HIMI — Cross-Domain Structural Validation

Load the ledger snapshot

The dashboard couldn't fetch ledger_recent.json automatically — that's expected when the page is opened straight from disk rather than served over http. Pick (or drop) your local ledger_recent.json and it will render exactly as it will in production.

Click to choose ledger_recent.json, or drop it here

Figure 5 · Hybrid quadrant classification

Ignition probability (PIE) →

Metabolic health (MDE) →

HIhealthy ignition EIexhausted ignition MCmetabolic collapse RRrecovery regime Nneutral

Recent trajectory · last N dispatches

— MDE PIE HIMI state ▾

Node inspector

Open data acknowledgments

NOAA NDBCMarine boundary-layer telemetry
ENTSO-E TransparencyEuropean grid actual-load
NASA GISS · GISTEMP v4Global temperature index

Classifications in window

—

published window

Window start

—

first anchored entry

Active domains

NOAA · ENTSO-E · NASA

Integrity

🛡Per-entry SHA-256

reproducible · not chain-linked

Bitcoin-anchored through

–

Showing the most recent 200 classifications per node — — of — in the published window. Each entry is self-contained and carries its own reproducible SHA-256 over its published fields — there is no chain linking entries yet, so we don't claim one. Click any row to recompute its result_hash in your browser and compare it to the published value. The full window is published as a downloadable, byte-recomputable artefact:

⇩ Download full window (ledger_full.json.gz) gzip · the complete published window, every entry recomputable — nothing is shown here that isn't in there.

Dispatch (UTC)	Node	Domain	MDE	PIE	State	result_hash (sha-256)
—

Hash verification

—

Source measured · dispatch received

—

Canonical payload — sha256(json.dumps({input_hash, state, ignition_probability, metabolic_health}, sort_keys=True)), floats at 8 dp

—

Recomputed in your browser (Web Crypto)

—

Published result_hash in the ledger

—

✓ Match — recomputed locally from the published fields, identical to the ledger value.

✗ No match — the recomputed hash differs from the published value.

Every value above is read from the public snapshot · the only thing computed in the browser is the SHA-256, so you can confirm it yourself. input_hash is the entry's vector_hash_sha256.

ⓘ Each HIMI classification writes a self-contained record with a reproducible SHA-256 over its published fields (input_hash = vector_hash_sha256, state, ignition_probability, metabolic_health, floats rounded to 8 decimals, keys sorted). The browser recomputes that hash with the Web Crypto API — byte for byte the same recipe the engine used server-side. This confirms the published record is intact and reproducible; it does not re-run the classification itself, since the engine is not exposed. The recorded state is displayed as-is from the ledger — the browser never re-derives it.