The Intranet of Things: Why Static Files Are Dead
Proposal_v1_KM.pdf
Proposal_v2_tracked_v4.pdf
Proposal_v3_final_client_review.pdf
Proposal_v4_final_FINAL_SIGNED_06092026.pdf
Every professional knows this exact sequence. Modern business operates inside a permanent graveyard of file versions. For three decades, the atomic units of knowledge work have been a handful of file extensions, frozen snapshots of information that become obsolete the moment someone hits save.
Cloud collaboration was supposed to fix this. Tools like Google Workspace, shared drives, and real-time multiplayer documents promised a cure for version control. In reality, cloud sharing just created a different kind of operational nightmare. Instead of hunting through email attachments, five different stakeholders are now simultaneously typing into a chaotic, blinking document, leaving fragmented comments, and accidentally deleting text. The result is a messy, unformatted whiteboard masquerading as a final business deliverable.
The underlying problem remains unchanged: corporate workflows still force complex, modern strategy into the digital equivalent of a flat sheet of paper.
But a radical shift is happening quietly, unnoticed by the broader market. It is currently visible only to a tiny fraction of a percent of insiders, engineers, and operators pushing the absolute boundaries of frontier AI. Thariq Shihipar, the engineering lead for Claude Code at Anthropic, exposed the massive bottleneck of our current documentation habits in his provocative piece, “Using Claude Code: The Unreasonable Effectiveness of HTML.” Shihipar argues that our reliance on simple Markdown and text files is a relic of an era with tiny context windows and expensive tokens. Instead of raw text files longer than a hundred lines that nobody actually reads, the future belongs to fully self-contained, single-page HTML files that link together into a unified index.
This is the genesis of the Intranet of Things. It is the realization that every piece of corporate collateral, sales materials, brand architectures, pitches, and proposals can exist as a dynamic, interactive micro-site. This reality was highlighted heavily on a recent episode of The AI Daily Brief titled “10+ Things You Should Build With AI Instead of Sending Files.” Host NLW laid out the immediate practical urgency: knowledge workers must stop sending static text files and start delivering living, shareable, updateable, interactive links. Recent breakthroughs, specifically OpenAI’s release of the "Sites" feature in Codex, mean that the technical barrier to building these functional web environments from plain text has completely dropped to zero.
Look at how information flows outside of work. Consumers naturally navigate responsive, interconnected web environments that serve up exactly what is needed based on real-time interaction. Enterprise collaboration systems must match this level of intelligence.
Revisiting business artifacts as living software changes everything.
Consider a strategic business proposal sent as a single link containing an embedded, interactive calculator. The client adjusts a few parameters to fit their budget, clicks a button, and the contract updates globally. The version control issues disappear because a single deployment link serves as the definitive source of truth.
A high-stakes creative pitch becomes a multi-layered site. The Chief Financial Officer can immediately dive deep into the interactive financial metrics, while the Chief Marketing Officer spends time exploring the embedded video prototypes. Everyone gets a tailored experience from a single URL, bypassing the need to sit through a forty-slide presentation sequentially.
Internal training works the same way through an adaptive portal that tracks progress, updates its own content globally the moment a system changes, and allows new hires to self-navigate the materials at their own velocity.
This transformation changes the role of the modern operator. Success is about speed, pattern recognition, and structural design. The ability to look at a complex organizational problem, rapidly prototype a functional link, and deploy it immediately is the ultimate competitive advantage.
The static file, even when hosted in the cloud, is a relic of an era when information was scarce and distribution was slow. Sending an attachment or a shared document link is simply leaving leverage on the table. The link is the asset. It is time to start building the network.
Sourced Content & References
HTML as the New Core Document: Shihipar, Thariq. (May 2026). “Using Claude Code: The Unreasonable Effectiveness of HTML.” Anthropic Claude Code Team / Lenny's Newsletter. Detailed engineering framework showing how self-contained HTML files replace raw text for interactive specifications, project roadmaps, and knowledge index trees. Technical Analysis by Simon Willison
The AI Operator Blueprint: Whittemore, Nathaniel (NLW). (June 7, 2026). “10+ Things You Should Build With AI Instead of Sending Files.” The AI Daily Brief: Artificial Intelligence News and Analysis. Exploring the death of corporate attachments via OpenAI’s "Sites" launch in Codex. Listen on Apple Podcasts