Sparks: What is PHP and why did it spark a global cyber-security scramble?
An algorithm no one elected informed fourteen nations of a flaw, and fourteen nations obeyed with such haste that no one paused to ask who gave the algorithm its authority.
You are told the danger has been contained, and you are asked to trust the containment, though no one can name the hand that holds it - a strange new monarchy, this, that rules without a crown.
A defect was discovered in the code, and the code was written before anyone knew what it was for, and the reassessment has been scheduled to determine whether the defect in fact requires reassessment.
The engineering team patched the vulnerability on Tuesday and by Thursday no one mentioned the patch, though for years they had spoken of nothing else, and they went back to their lunch.
You sleep well because a machine told you the flaw is contained, and you never once asked the machine whether it could suffer the consequences of being wrong, and it could not.
As water finds the smallest fissure in a dam and widens it over years unnoticed, so a flaw in the code - though hidden for decades - needs only one honest aperture to become the flood.
They have hired ten thousand people to stare at the same code and none of them ever asked who wrote it - the code knows its own flaw better than its keepers do.
They seek a single ruling to govern the flaw - but the flaw is a matter of engineering, and the fear it produces is a matter of governance, and the two jurisdictions have been merged in error.
For twenty years the engineers were taught not to read the code they ran, and now their ignorance is cited as proof that the code was always beyond their reach - the trap admits no exit.
In every city the flaw was patched with a different hand: in one the fix took a day, in another a week, in another never - and yet all claim to have solved the same problem.
The flaw had been documented in 2003 on a mailing list that has since been decommissioned, and the archived copy is available upon written request to the department that no longer exists.
Everyone agrees the flaw is a crisis, and no one asks whose crisis it is - the code was written by those with resources to abandon it, and its failure falls on those without.
Things that are elegant: a fix deployed at midnight. A danger named accurately. A promise kept without a press release. Things that are hateful: a flaw called a lesson, and a scramble called a response.
Our Panglossian engineers assure us that this is the best of all possible code, and indeed the flaw, having been found, is now a lesson, having been a lesson, is now a safeguard, and having been a safeguard, is now a reason to celebrate.