Skip to main content
All articles
AI & Transformation7 min readSeptember 29, 2026

The Decision Desk Pair: Barometer and Binnacle

Two decision desks. Two domains. One architecture. The Glass reads the barometer for tropical storm operations. The Binnacle steers by the Sun for space-weather operations. Both seal every decision in a SHA-256 hash chain linking the call to the instrument state that informed it. The decision survives the event because it was recorded before the event arrived.

Two operators. Two clocks. Two instruments. The same question.

The marina manager watches a tropical storm approach and must decide when to haul out the boats. The grid controller watches a coronal mass ejection approach and must decide when to shed load at 78°N. Neither of them can wait for certainty. Both of them must prove, after the event, what they knew and when they decided.

The Glass and The Binnacle exist for these two operators. One reads the barometer. The other steers by the Sun. Together, they form a decision desk pair that applies the same evidence architecture to two domains where the stakes are physical, the timeline is hours, and the record must survive the event.

The Glass: read the barometer

The Glass is a tropical storm decision desk.

The forecast layer. Fifty NHC ensemble members coloured by wind intensity. The spread is the forecast — where the members agree, confidence is high. The official NHC cone alongside a Google DeepMind AI track overlay, with the gap measured in nautical miles. Probability terrain showing 34/50/64-knot wind coverage. Issuance cycle history scored against actual tracks.

The operator layer. Four personas — marina, port, people, watch — each with site-specific wind thresholds and rule-based triggers. The rules are sealed in the genesis block before the storm arrives.

The evidence layer. Genesis block (rules) → snapshot blocks (ensemble state, probability, NHC advisory, AI prediction) → decision blocks (action, authority, probability data). SHA-256 hash chain. Every block covers the prior.

Three real 2026 storms — POLO, NOLO, FAY — from live NHC a-deck data.

The Binnacle: steer by the Sun

The Binnacle is a space-weather decision desk.

The forecast layer. Coronal mass ejections displayed on the Sun-Earth line using the Vršnak et al. (2013) drag-based propagation model. Magnetopause rendered from measured solar wind using Shue et al. (1998). Auroral oval driven by Kp index with NOAA OVATION overlay. Independent forecast runs maintained as distinct issuances — temporal layers showing how the forecast evolved.

The operator layer. Five scenarios — grid (load shedding at 78°N), polar flight (HF blackout forces track south), satellite (shield crossing at 6.6 Re triggers safe mode), survey (GNSS precision loss halts work), timing (scintillation forces oscillator holdover) — each with threshold-triggered actions.

The evidence layer. Genesis block (site rules, Kp triggers) → snapshot blocks (solar wind speed/density/Bz, Kp, magnetopause standoff, CME arrival outlook) → decision blocks (action, instruments, authority). SHA-256 hash chain. Same architecture as The Glass.

428 CMEs and 352 forecast runs from NASA DONKI.

Same architecture, different instruments

The two desks share every structural element except the instruments they read:

ElementThe GlassThe Binnacle
DomainTropical stormsSpace weather
InstrumentNHC ensemble + AI modelNASA DONKI CME catalogue + solar wind
Forecast model50-member ensemble spreadDrag-based CME propagation
UncertaintyCone + probability terrainArrival timing ±12-hour error band
OperatorsMarina, port, people, watchGrid, polar flight, satellite, survey, timing
ThresholdsWind speed (kt)Kp index, magnetopause standoff (Re)
EvidenceSHA-256 hash chainSHA-256 hash chain
GenesisWind rules sealed before stormKp rules sealed before CME
SnapshotEnsemble + NHC + AI stateSolar wind + Kp + magnetopause state
DecisionAction + probability + authorityAction + instruments + authority

The architecture is identical. The physics is different. The operator is different. The evidence standard is the same.

Why decision desks, not dashboards

A dashboard shows data. A decision desk records decisions against data.

The distinction matters because of what happens after the event. The insurance adjuster who arrives after the storm does not ask "what was the wind speed?" They ask "what did you know, when did you know it, and what did you decide?" A dashboard cannot answer that question. It shows the current state. It does not preserve the state at the moment of decision.

The Glass and The Binnacle preserve that state. The genesis block seals the rules before the event. The snapshot block captures the instrument state at the moment of decision. The decision block records what was decided, by whom, based on which snapshot. The hash chain links them immutably.

The decision survives the event because it was sealed before the event arrived.

Where the pair fits in the portfolio

The decision-intelligence category now has four products:

  • KEEL — decision provenance for PE portfolios. The Conviction Ledger.
  • MAP//DO — AI work navigator. Outcome workspace.
  • The Glass — tropical storm decision desk. Read the barometer.
  • The Binnacle — space-weather decision desk. Steer by the Sun.

The first two serve institutional decision-making under strategic uncertainty. The last two serve operational decision-making under environmental uncertainty. All four produce hash-chained decision records. All four answer the same question: can you prove what you decided, and why?

What neither desk does

Neither desk issues warnings. Official watches and warnings come from NHC, CPHC, NWS (tropical storms) and NOAA SWPC (space weather). The Glass and The Binnacle are decision rehearsal instruments. They help operators see the full picture, apply pre-agreed rules, and seal the call.

The authority is the operator. The instrument informs. The record proves.


Both desks are live and free to use.

Open The Glass → — read the barometer.

Open The Binnacle → — steer by the Sun.

Explore the full portfolio →

Richard Leclézio

Richard Leclézio

Enterprise Transformation & AI Delivery Leader

ShareLinkedInX