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
DEC PDP-10 pixel portrait
⬡ Pioneer◉ Voicefame

DEC PDP-10

Digital Equipment Corporation PDP-10 / DECSYSTEM-20

The Machine That Raised the Hackers

sixties · 3 min read · Decommissioned
“You could tell how good a programmer was by whether they had a login on the AI lab PDP-10.”

The Machine

The PDP-10 was introduced by Digital Equipment Corporation in 1966. Its 36-bit word size was not an accident: 36 bits is evenly divisible by 6 (for 6-bit characters), by 9 (for 9-bit bytes), and allowed efficient representation of both text (packed characters) and floating-point numbers. The architecture was designed by Gordon Bell and others who had thought carefully about what a general-purpose computing machine should optimize for.

TOPS-10 and TOPS-20 (via the TENEX operating system from BBN) gave the PDP-10 powerful timesharing and interactive capabilities. Multiple users could log in simultaneously, run programs independently, and share files. This sounds obvious today. In the 1960s, it was radical — computers were batch-processing machines that ran one job at a time from a card reader queue.

Where Hacker Culture Was Born

MIT's Project MAC (Mathematics and Computation) ran on a PDP-10. The MIT AI Lab ran on PDP-10s into the 1980s. SAIL (Stanford Artificial Intelligence Laboratory) ran on a DECSYSTEM-20. These machines were the common ground of the early hacker community — the people who would go on to create Unix, Emacs, Lisp, the TCP/IP stack, and the foundations of the modern internet.

The interactive timesharing environment created by the PDP-10 operating systems was conducive to a specific working style: exploratory, immediate, collaborative. You could test a function interactively. You could read other users' code (if they hadn't set file protections — and often they hadn't, because sharing was the norm). You could leave programs running and come back. The culture of "release early, share widely, improve collaboratively" that the open-source movement formalized was simply the normal working environment on a PDP-10.

Emacs — the extensible text editor that remains in active use today — was first written for a PDP-10 at MIT in 1976. MACLISP, the dialect of Lisp that led directly to Common Lisp and influenced JavaScript, Scheme, and Python, ran on PDP-10s. Zork, the text adventure game that launched the interactive fiction genre, was written on a PDP-10 at MIT.

The Death

DEC discontinued PDP-10 development in 1983, prioritizing the VAX architecture. The MIT AI Lab held a funeral for their PDP-10 (named "ITS" — Incompatible Timesharing System). Richard Stallman, who had spent years on the MIT AI Lab PDP-10, responded to the machine's death and the proprietary software that replaced it by beginning work on the GNU Project — a free software operating system. The death of the PDP-10 is the direct ancestor of the free software movement.

The PDP-10 was not replaced because it was inferior. It was replaced because DEC made a business decision. The hackers who lost access to it built the internet instead. The outcome was not planned. It was a consequence.