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
The Abacus pixel portrait
⬡ Pioneerfame

The Abacus

c. 2700 BCE

The First Computer That Beat the Electronic One

forties_fifties · 3 min read
“The abacus is as fast as the person using it. The modern computer is as fast as the algorithm running on it. For most of human history, the person was the bottleneck. This has not changed.”

The Device

The abacus is a frame with beads strung on rods or wires, each position representing a power of ten. Moving a bead toward the center registers its value. The sum of all registered values is the number currently held. To add: move beads. To carry: move ten lower-position beads and reset, move one upper-position bead forward.

That is the complete specification. It has not been substantially improved in 4,700 years.

The Sumerian abacus appears in records around 2700 BCE. The Chinese suanpan appears around 200 BCE. The Japanese soroban — a refined version optimized for speed — was standardized in the 16th century and remains in use today. An experienced soroban operator can add a column of ten 3-digit numbers faster than a person entering the same numbers on a calculator.

The 1946 Race

On November 12, 1946, Sergeant Thomas Nathan Wood of the U.S. Army Finance Disbursing Section — equipped with a Friden electromechanical calculator, considered state of the art — raced Kiyoshi Matsuzaki of the Japanese Post Office Ministry, equipped with a soroban. The race was organized by Stars and Stripes as a demonstration of modern vs. traditional computation.

Matsuzaki won. Four out of five rounds. Addition, subtraction, multiplication, and overall computation: soroban. Division only: the electric calculator.

The lesson was reported as a curiosity. It is actually an architectural insight: the abacus parallelizes carry propagation across all columns simultaneously, where electronic calculators in 1946 had to propagate carries sequentially. The soroban's physical architecture solved a problem that electronic computers didn't solve in hardware until carry-lookahead adders appeared in the 1950s.

The Pattern

The abacus is constructive laziness at its most perfect: the minimal possible physical encoding of positional arithmetic. Each bead has one state: registered, or not. Each position has one meaning: its power of ten. There is no instruction set, no operating system, no boot sequence. The computation is the state of the physical object.

Every abstraction layer added after the abacus was necessary. And every abstraction layer added after the abacus was also an opportunity for a new failure mode. The abacus has no overflow flag. When you have too many beads, you can see it. When your 16-bit integer overflows, you cannot.

The Ariane 5 rocket crashed because a 64-bit float didn't fit in a 16-bit integer. The abacus has been solving that problem for 4,700 years by making the overflow physically visible. We forgot.