Datageddon — how data disasters become Armageddon disasters#
A datageddon is a disaster made of overlooked data: records lost, research defunded, maintenance skipped, a warning filed and forgotten, a hard problem declared “not my job.” Each one looks small. The claim of this page — and the reason the author named his lab the Datageddon Armageddon Research Lab (DARL) — is that these small, ignored failures compound, and that their end state, if nobody cleans them up, is Armageddon-scale: the cascading, civilisation-ending kind of disaster, up to and including accidental nuclear winter.
You do not need any theology to see the mechanism. It is ordinary systemic risk: a neglected fault propagates into the system that depends on it, which propagates into the system that depends on that, until a local “nothing” has become a global everything. The dismissed is the most dangerous category there is, precisely because no one is watching it.
Why this needs a ResearchCity#
If datageddons are the disease, the cure is an institution whose actual job is to clean them up at scale — to find the overlooked, fund the unfunded, keep the knowledge no single quarter rewards, and work patiently through the hard cases everyone else has written off. That institution is ResearchCity. It scales up over 7-8 stages in time, into as many as the 1600 research stadia in space (the 1600 stadia of Revelation 14:20); stages and stadia are fully orthogonal. How that scale-up works — and why it must be co-located in one city — is set out on the ResearchCity page.
The Jubilee System is what keeps work from being wasted over the long term.
An example, where it gets personal: the Datageddon Wall of Revelation#
Optional, and where the secular account hands over to a personal one — skip it freely; nothing above depends on it.
Why a cleanup lab keeps a “Revelation” stadion. I would never have proposed anything like ResearchCity if the book of Revelation had not inspired the hypothesis — which then had to be worked out and audited like any other. (Think of Kekulé’s dream of a snake biting its own tail: the dream was not chemistry, but the benzene-ring experiments it inspired are what moved the needle. The inspiration is never the proof; the work is.) Revelation is not simple — some of humanity’s best minds gave up on it — but since a society’s future runs along its eschatology, it would be a disservice for ResearchCity not to dedicate one research stadion to the “endtime” questions so many people carry. STa4-REV is that stadion (one of the 16 initial topic-stadia). Its aim is to align how all the world’s eschatology insights relate — a hairball whose computational challenge is an Evolvix syntax and compiler that can hold it without breaking (the language design belongs to STa1-EVX, the live test to STa4-REV; neither succeeds without the other). An overview of all 16 stadia is in the Transwarp Key.
The hardest “datageddon” the author tried to clean up himself was an old one: the book of Revelation, a text widely treated as a disaster of meaning — decrypted by no one for two millennia, and read, where it is read at all, as a prophecy of doom. In 2022 he assembled a physical Datageddon Wall of Revelation — a wall of books — to test whether it could instead be read as a coherent, non-violent strategic map. That wall is the seed-bed of everything that followed: first the MMv3 Good News Pack (2025), then the auditable MMv5 Matheo Study Series (2026) — the same ideas re-poured, each time, into a more navigable and more checkable form. Whether that reading holds is exactly the kind of thing the author asks others to audit.