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
Compaq pixel portrait
⬡ Pioneer⬢ Builderfame

Compaq

Compaq Computer Corporation

The Clone That Broke IBM's Lock

eighties · 3 min read · Decommissioned
“We didn't steal anything. We reverse-engineered it, documented every step, and beat them in court. That's how innovation works.”

The Napkin

In 1981, Rod Canion, Jim Harris, and Bill Murto were engineers at Texas Instruments, frustrated by TI's direction. They met at a House of Pies restaurant in Houston to discuss starting a company. Canion sketched a design for a portable IBM-PC-compatible computer on a paper placemat. The sketch showed a sewing machine-style briefcase form factor with a flip-up display.

They raised $1.5 million from venture capital and started Compaq Computer Corporation in 1982.

The critical engineering challenge was not the hardware. It was the BIOS — the Basic Input/Output System, the firmware layer between the operating system and the hardware. IBM's BIOS was copyrighted. Using it directly was infringement. The solution was clean-room reverse engineering: two teams, completely separated with no communication, documented only by a specification written from IBM's public documentation. Team A analyzed IBM's BIOS and wrote a complete functional specification of what it did, without any IBM code. Team B, who had never seen the IBM BIOS, wrote a new BIOS that matched Team A's specification.

Compaq's lawyers documented every step of this process specifically to demonstrate in court that no IBM code was used. The strategy held. IBM sued. Compaq won.

What the Clone Created

The Compaq Portable shipped in 1982, the same year the company was founded. It weighed 28 pounds, displayed text on a 9-inch CRT, ran MS-DOS, and was fully IBM-compatible. It ran every IBM PC program. It sold 53,000 units in its first year — $111 million in revenue, a first-year record at the time.

The clone market that followed destroyed IBM's hardware leverage. Once compatible PCs could be built legally, the price war was inevitable. By the mid-1980s, dozens of manufacturers were producing IBM-compatible PCs. IBM had contributed the architecture. It could not charge rent on it. The economic value migrated to Microsoft (the software) and Intel (the processor), both of which IBM had allowed to sell to third parties in the original deal.

Compaq was acquired by HP in 2002.

The Exhibit

Compaq's story is the museum's exhibit on unintended architectural consequence: IBM designed a modular, open-architecture PC — because that was faster to ship — and didn't foresee that the modularity made it legally cloneable. The architecture that allowed IBM to launch quickly is the architecture that made IBM's competitive position impossible to defend.

IBM opened the architecture to ship faster. Compaq opened the market to compete. The lesson is not that IBM was wrong. The lesson is that architectural decisions carry competitive consequences their designers don't control.