Consilient Network· The graph of everyone who built this · Add your entry ↗
The Graph · Concept

MR-DIBS: the nuclear-plant resiliency test Hare applied to his own company — and the one failure mode it missed

Multiple Redundant, Independent, Backup Systems — developed at Impell for nuclear safety software, applied to everything since

About this entry

This is Jonathan Hare's account, with its provenance shown. The person or organization named has not yet claimed or corrected it.

Concept

What this is

MR-DIBS — Multiple Redundant, Independent, Backup Systems — is the resiliency criterion Jonathan Hare developed at Impell Corporation, writing software to manage and assess safety systems for nuclear power plants (Impell being a unit of Combustion Engineering, later acquired by ABB in Zurich, where the friendships continued). The test: no single failure should be able to take the system down, because every critical function has independent, redundant backing. By late 2000, Consilient looked like it passed — multiple blue-chip customers, multiple partnership tracks, multiple competing term sheets, multiple banking relationships. Hare's own retrospective verdict on the confidence this produced is preserved verbatim in the source record: he became convinced, in the era's phrase, that his shit no longer stank.

The instructive part is what the criterion missed, and the record states it because the architecture is built on the lesson: every one of Consilient's redundant systems was independently exposed to the same environment. When the bubble burst and 9/11 followed, the customers cut budgets together, the term sheets evaporated together, and the banks retrenched together. Redundancy within a correlated environment is not redundancy — a truth nuclear engineering states as common-cause failure, and the reason the Quantum Privacy Network's resilience story is built on structural independence at the substrate, not on counting backups that share a sky.

The graph

Connected from here

There is no single root. This is one view of the graph, from this node — what you see depends on where you enter and what you are looking for.

Provenance

Where this came from

Everything above is a distillation. The primary source is published in full, so that any claim on this page can be walked back to what was actually said — and where the two differ, the source governs.

Claim your edge

What is missing, and how to fix it

This entry is deliberately incomplete. The gaps below are the things only certain people can settle — and settling one is a contribution like any other: recorded, timestamped and attributed to whoever made it.

If you were there

Correct anything wrong, add what only you know, or claim this entry as your own. Write to evidence@qpncatalyst.io and Jonathan directly (both are on the button) — a timestamped confirmation comes back with your submission attached, as your own independent record. No account, no permission, no institutional standing required.

Public contributions earn Publicity Premium; bringing others who were there earns Cascade Premium. Everything is valued retrospectively as outcomes verify, so nothing has to be priced up front.

Correct this entry → Add a story, photo or link → Browse the graph →
Where this leads

Pull the next thread

Share this
Share this page: X · LinkedIn · Email · Copy link
← PreviousAll entities
+ Add to the record