Museum Wire
Law 0 · Katie's LawEvery system is shaped by the human drive to do less work. This is not a flaw. It is the economic force that produces all software — and all software failure.◆Law I · Boundary CollapseWhen data crosses into a system that interprets structure, without being constrained, it becomes executable.◆◆ 2026 IncidentAxios. 70 Million Downloads a Week. North Korea Inside.◆Law II · Ambient AuthorityWhen a system trusts the presence of a credential instead of verifying the intent behind it, authentication becomes indistinguishable from authorization.◆◈ AXM-001Set Theory — Membership, Boundaries, and Belonging◆Law III · Transitive TrustWhen a system inherits trust from a source it did not verify, the attack surface extends to everything that source touches.◆◆ 2026 IncidentClaude Code — The Accept-Data-Loss Flag◆Law IV · Complexity AccretionSystems do not become complex. They accumulate complexity — one reasonable decision at a time — until no single person can hold the whole in their head.◆Law V · Temporal CouplingCode that assumes sequential execution, stable state, or consistent timing will fail the moment concurrency, scale, or latency proves the assumption wrong.◆◆ 2026 IncidentCopy Fail — 732 Bytes to Root on Every Linux Distribution◆◈ AXM-002Boolean & Propositional Logic — True, False, and the Excluded Middle◆Law VI · Observer InterferenceWhen the system that monitors health becomes a participant in the system it monitors, observation becomes a failure vector.◆◆ 2025Amazon Kiro — The 13-Hour Outage◆◆ 2025Operation Chrysalis: The Notepad++ Supply Chain Hijack◆◆ 2025Replit Agent — The Vibe Code Wipe◆◆ 2025Shai-Hulud — The npm Worm That Ate Its Own Ecosystem◆◆ 2024Air Canada Chatbot — The Policy That Wasn't◆◆ 2024Change Healthcare — One-Third of US Healthcare, One Missing MFA◆◆ 2024CrowdStrike — The Security Update That Broke the World◆◆ 2024Google Gemini Image Generation — The Six-Day Pause◆◆ 2024XZ Utils — The Two-Year Infiltration◆◆ 20233CX — The Supply Chain That Ate Another Supply Chain◆◆ 2023Amazon Prime Video — The Per-Frame State Machine◆◆ 2023Bing Sydney — The Chatbot That Went Rogue◆◆ 2023Samsung ChatGPT Leak — The Employee Who Pasted the Secret◆EFFODE · LEGE · INTELLEGE◆Law 0 · Katie's LawEvery system is shaped by the human drive to do less work. This is not a flaw. It is the economic force that produces all software — and all software failure.◆Law I · Boundary CollapseWhen data crosses into a system that interprets structure, without being constrained, it becomes executable.◆◆ 2026 IncidentAxios. 70 Million Downloads a Week. North Korea Inside.◆Law II · Ambient AuthorityWhen a system trusts the presence of a credential instead of verifying the intent behind it, authentication becomes indistinguishable from authorization.◆◈ AXM-001Set Theory — Membership, Boundaries, and Belonging◆Law III · Transitive TrustWhen a system inherits trust from a source it did not verify, the attack surface extends to everything that source touches.◆◆ 2026 IncidentClaude Code — The Accept-Data-Loss Flag◆Law IV · Complexity AccretionSystems do not become complex. They accumulate complexity — one reasonable decision at a time — until no single person can hold the whole in their head.◆Law V · Temporal CouplingCode that assumes sequential execution, stable state, or consistent timing will fail the moment concurrency, scale, or latency proves the assumption wrong.◆◆ 2026 IncidentCopy Fail — 732 Bytes to Root on Every Linux Distribution◆◈ AXM-002Boolean & Propositional Logic — True, False, and the Excluded Middle◆Law VI · Observer InterferenceWhen the system that monitors health becomes a participant in the system it monitors, observation becomes a failure vector.◆◆ 2025Amazon Kiro — The 13-Hour Outage◆◆ 2025Operation Chrysalis: The Notepad++ Supply Chain Hijack◆◆ 2025Replit Agent — The Vibe Code Wipe◆◆ 2025Shai-Hulud — The npm Worm That Ate Its Own Ecosystem◆◆ 2024Air Canada Chatbot — The Policy That Wasn't◆◆ 2024Change Healthcare — One-Third of US Healthcare, One Missing MFA◆◆ 2024CrowdStrike — The Security Update That Broke the World◆◆ 2024Google Gemini Image Generation — The Six-Day Pause◆◆ 2024XZ Utils — The Two-Year Infiltration◆◆ 20233CX — The Supply Chain That Ate Another Supply Chain◆◆ 2023Amazon Prime Video — The Per-Frame State Machine◆◆ 2023Bing Sydney — The Chatbot That Went Rogue◆◆ 2023Samsung ChatGPT Leak — The Employee Who Pasted the Secret◆EFFODE · LEGE · INTELLEGE◆
Keyboard Navigation
W↑
A←
S↓
D→
or arrow keys · M for map · Q to exit
← Back to Hall of Heroes
Alan Turing pixel portrait
⬡ Pioneer◆ Breaker⬢ Builderfame

Alan Turing

@turing

Father of Theoretical Computer Science

1930s–1950s · 2 min read · Decommissioned
“We can only see a short distance ahead, but we can see plenty there that needs to be done.”

The Story

Alan Turing's 1936 paper "On Computable Numbers" didn't describe a machine — it described the limits of all possible machines. The Turing machine was a thought experiment that formalized what it means to compute, proving that some problems are undecidable and that a single universal machine could simulate any other.

During World War II, he led the team at Bletchley Park that broke the Enigma cipher — arguably the first large-scale cryptanalysis operation and the first demonstration that computational thinking could be applied to security at a national scale. The Bombe, the electromechanical device his team built, was a special-purpose breaker — a machine designed to find the flaw in another machine's logic.

After the war, he designed the ACE (Automatic Computing Engine) at the National Physical Laboratory — one of the earliest stored-program computer designs. He wrote what may be the first chess-playing algorithm, simulating it by hand before any computer could run it.

In 1950, he published "Computing Machinery and Intelligence," proposing the Turing Test and asking whether machines could think — launching the field of artificial intelligence.

In 1952, he was prosecuted for homosexuality, subjected to chemical castration, and died in 1954. He was pardoned posthumously in 2013. The "Alan Turing law" retroactively pardoned thousands of others convicted under the same statute.

Why They're in the Hall

Turing is Pioneer, Breaker, and Builder simultaneously.

Pioneer: He formalized computation before computers existed. Every programming language, every algorithm, every exhibit in TechnicalDepth operates within the theoretical framework he defined. The concept that a program is a sequence of symbols manipulated by rules — that's Turing.

Breaker: Enigma was a cryptographic system that its designers believed was unbreakable. Turing's team found the pattern — the structural flaw in how operators used the machine — and exploited it. This is software archaeology at its most consequential: finding the pattern in someone else's system, understanding why it was built that way, and using that understanding to break it.

Builder: The ACE, the Bombe, the chess algorithm — Turing didn't just theorize. He built. And his designs influenced every machine that followed.

His persecution and death are a reminder that the history of computing is not just a history of machines. The people who built this field were human, and the institutions they worked within had flaws far worse than any documented in the Exhibits wing.