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
IBM AS/400 pixel portrait
⬡ Pioneer⬢ Builderfame

IBM AS/400

IBM AS/400 / iSeries / IBM i

The Computer That Refuses to Die

eighties · 3 min read
“If it ain't broke, don't replace it. The AS/400 banking systems running today were written by people who are now retired. The software is still correct.”

The Machine

The IBM AS/400 was introduced June 21, 1988. It was designed as a midrange business computer — between mainframes and personal computers — with a clean-sheet architecture that made several unusual engineering commitments:

Technology Independent Machine Interface (TIMI): programs compiled for the AS/400 compiled to an intermediate representation that was translated to actual machine code at runtime. This meant that when IBM changed the underlying processor architecture (from CISC to PowerPC in 1995), existing compiled programs continued to run unmodified — they were retranslated. No recompilation required. No source code changes required. Existing applications: unaffected.

Object-based single-level storage: the AS/400 treats all objects — files, programs, user data, system objects — as part of a single address space managed by the operating system. There is no file system in the traditional sense. The system manages storage, handles backups, and maintains object integrity automatically. This architecture eliminated entire classes of security vulnerabilities that operating system file security has struggled with for decades.

Why It Never Dies

Walk into a regional bank, a mid-sized manufacturer, or a government agency. Somewhere in their data center there is a machine running IBM i. The application running on it was likely written in RPG or COBOL between 1990 and 2005 by programmers who may no longer work there. It runs correctly. It has run correctly every business day since it was deployed.

The AS/400 backward compatibility commitment means that software written for the original 1988 platform — compiled 35 years ago — runs on modern Power10 hardware without modification. This is not a theoretical claim. It is documented in production deployments around the world.

This is the museum's exhibit on what correct engineering looks like in practice: a platform that made backward compatibility a first-order architectural constraint, paid an engineering cost to implement it thoroughly, and earned a 35-year track record of unbroken production deployments.

The Pattern

The AS/400's longevity is the constructive counterpoint to every exhibit in the museum. Where Complexity Accretion documents software accumulating technical debt that eventually breaks under its own weight, the AS/400 documents a platform that managed the complexity horizon through abstraction layers that were designed, not accumulated.

The TIMI layer is the key: it separates what the application does from how the hardware does it. Every time IBM changed the underlying hardware, the applications were unaffected because the abstraction layer absorbed the change. This is the same principle that makes Java "write once, run anywhere" — but the AS/400 implemented it in 1988, proprietary, and made it work for 35 years of hardware generations.

There are AS/400 applications older than most software engineers running in production today. The software is not wrong. Katie's Law explains why modern systems aren't this durable: making backward compatibility a first-order commitment is hard. The AS/400 team did the hard work. Most teams don't.