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

The Quipu

c. 3000 BCE

The Knotted String Database Nobody Could Fully Decode

forties_fifties · 2 min read · Decommissioned
“The quipu is a database we cannot read because we lost the schema. Every deprecated API without documentation is a quipu.”

The Device

A quipu is a main cord, suspended horizontally, from which pendant cords hang. Each pendant cord may have subsidiary cords. Each cord may have sub-subsidiary cords. The hierarchy can extend multiple levels. Knots on each cord encode numbers in a decimal positional system: knot position indicates magnitude (ones, tens, hundreds, thousands), knot type indicates digit (figure-eight knot for 1, long knot with number of turns for 2-9, and so forth). Cord color and ply direction carry additional information.

The Inca Empire administered a territory of 2 million square kilometers — running from present-day Colombia to Chile — without writing, using quipus maintained by trained specialists called quipucamayocs. Census records, tax collection, military logistics, agricultural inventories: all managed through the knotted string system.

The Schema Problem

Here is the exhibit: archaeologists can read the numerical quipus. The positional encoding is mathematically consistent and has been decoded. When a quipu contains pure decimal number sequences, modern scholars can read them.

Approximately 20% of surviving quipus do not follow the numerical schema. Their knot patterns are consistent — they are clearly encoding something systematically — but the encoding has not been recovered. These may be narrative quipus, encoding historical events, official decrees, or information categories scholars haven't identified. Or the schema may have been carried in the quipucamayoc tradition, passed orally, and died with the tradition.

The Spanish colonizers explicitly destroyed quipus as part of the suppression of Incan culture. Document destruction as epistemicide. The schema for the non-numerical quipus may have survived intact until the 16th century and was then deliberately eliminated.

The Museum Lesson

The quipu is the oldest example of data without documentation: a complex, internally consistent encoding system where the data survives and the schema does not. Every organization that has ever inherited a database with no data dictionary, every developer who has opened a legacy system with no README, every archaeologist of broken software has stood in the same position as the scholars staring at a non-numerical quipu.

The data is there. The encoding is systematic. The key is gone.

Katie's Law: it was too much work to write down what the knots meant. The quipucamayocs knew. They would always know. And then they didn't.