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
Tim Berners-Lee pixel portrait
⬡ Pioneer⬢ Builderfame

Tim Berners-Lee

@timbl

Inventor of the World Wide Web

1990s · 3 min read
“The web is more a social creation than a technical one. I designed it for a social effect — to help people work together — and not as a technical toy.”

The Story

In 1989, a British scientist at CERN named Tim Berners-Lee wrote a proposal titled "Information Management: A Proposal." His supervisor's response, written on the cover page, was: "Vague but exciting." It was the most consequential understatement in the history of technology.

Berners-Lee was trying to solve a mundane problem: researchers at CERN couldn't easily share documents across different computer systems. His solution combined three ideas that already existed in isolation — hypertext, networked protocols, and domain naming — into something that hadn't existed before: the World Wide Web.

He created HTTP (a protocol for requesting and serving documents), HTML (a markup language for structuring them), and URLs (a universal addressing scheme for locating them). He built the first web browser and the first web server, both running on a NeXT computer at CERN. The first website went live on December 20, 1990.

Then he did something that shaped everything that followed: he gave it away. Berners-Lee convinced CERN to release the web's underlying technology with no patents, no licensing fees, no restrictions. Anyone could build a web server. Anyone could build a browser. Anyone could create a web page and link it to any other page on Earth without asking permission.

This openness was a design philosophy, not an oversight. The web was permissive by default. You could view the source of any page. Forms could POST to any URL. There was no authentication layer built into HTTP. Links were one-directional — the page you linked to didn't know you'd linked to it. The web trusted its users by default and imposed almost no constraints on what they could do with it.

Berners-Lee went on to found the World Wide Web Consortium (W3C) to steward web standards, and has advocated for net neutrality, open data, and web accessibility throughout his career. He was knighted in 2004 and received the Turing Award in 2016.

Why They're in the Hall

Berners-Lee is Pioneer and Builder on a scale that's difficult to overstate. He built the platform that every web-era exhibit in TechnicalDepth runs on.

His connection to TechnicalDepth is structural. The web's permissive design — the same openness that made it possible for anyone to publish, link, and build — is the source of entire categories of vulnerabilities. Cross-site scripting exists because HTML mixes content and code. SQL injection exists because forms POST user input that gets concatenated into queries. Cross-site request forgery exists because browsers automatically attach credentials to requests. SSRF exists because servers can be tricked into making requests on an attacker's behalf.

None of these are bugs in Berners-Lee's design. They're consequences of his core principle: the web should be open, permissive, and free of gatekeepers. Every security flaw in the injection domain is, at its root, a tension between that principle and the reality that not all users are trustworthy.

The web's "view source" feature — the ability to inspect how any page is built — is arguably the most powerful educational tool in computing history. Millions of developers learned HTML, CSS, and JavaScript by right-clicking and reading someone else's code. This is software archaeology at its most democratic: the system invites you to study it.

Berners-Lee designed the web for a social effect, not as a technical toy. The social effect exceeded anyone's imagination. So did the consequences. TechnicalDepth documents both — the patterns the web enabled and the flaws its openness introduced. Every one of them traces back to a proposal that a CERN supervisor called "vague but exciting."