--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/41/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/41/echoes" issue: 41 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Sevda Polat","Sable Whitford"] published: 2026-08-10 updated: 2026-08-06 articles: 15 --- # TinyFish > CURRENT is a journal about AI agents in production, for the engineering and product leaders who have to make them work. Drawing on experience building enterprise web agents, it explains why the demo succeeded and the deployment didn't, and what that means for choosing vendors, briefing the board, and avoiding mistakes others have already made. [Read on the website]() ## Issue 41 — Echoes Past infrastructure decisions echoing in today's production realities ### Network Ignorance - [The Network Was Built Not to Know]() — By [Sevda Polat]() · Published 2026-08-05 · Format: Network Ignorance Three engineers argued in 1984 that only the two ends of a conversation can judge whether an exchange came out right. TCP/IP took the advice. What we got is a network that moves a purchase, a regulatory disclosure, and a video of somebody's dog through the same machinery, which is precisely why anyone could build anything on it without asking permission first. The paper also asked a question it declined to answer: where are the ends? Agents now sit there, checking outcomes against a standard held by a principal who never saw the choice being made. ### The Road Refused - [The Network That Knew Who Was Talking]() — By [Sevda Polat]() · Published 2026-08-05 For most of a century the telephone network knew who was talking. A call reserved a physical path and held it: two identified endpoints, a start time, a route, an explicit hang-up. By the late 1970s the signaling layer underneath tracked all of that well enough to bill you by the second. The relationship between two people talking was something the network itself maintained. ### Carrying Without Knowing - [Gil Hopsworth on Routing Packets for Thirty Years Without Asking Why]() — Published 2026-08-05 *The internet was built on a principle so elegant it reads like philosophy: the network should not understand what it carries.* In their 1984 paper, Saltzer, Reed, and Clark argued that functions like reliability, security, and correctness "can completely and correctly be implemented only with the knowledge and help of the application standing at the endpoints." The network moves packets. Everything else belongs to the edges. ### Intelligence Returns - [The Middle of the Network Wanted to Know]() — By [Sevda Polat]() · Published 2026-08-05 · Format: Intelligence Returns Traffic does not declare what it is for. There is no field for that, and there never was — so when broadband operators bought equipment to read inside the packets they carried, the machinery had to guess: from sizes, from timing, from patterns of bytes recurring at line rate. A 2008 FCC case shows what a guessing engine can do once it is sitting on the rack. Encryption's reply had no way to tell the honest operators from the opportunistic ones, and made no attempt. - [Your Browser Believes the Edge Is the Site]() — By [Sevda Polat]() · Published 2026-08-05 · Format: Intelligence Returns Distributed caching entered the world in 1997 as a load-balancing result: how to keep everyone wanting the same file at once from melting a single server. Encryption changed what that position means. To serve a site over HTTPS, the machine nearest you has to hold credentials in the site's own name, which means your browser treats it as the party it was talking to all along. The reading that encryption drove out of the middle of the network found somewhere it is welcome. ### Further Signals - **End-to-End Arguments in System Design** — [Source]() — Published 2026-08-05 Saltzer, Reed, and Clark's 1984 paper on where network intelligence belongs — still shaping infrastructure arguments today. - **Paul Baran and the Origins of the Internet** — [Source]() — Published 2026-08-05 RAND's Cold War survivability research produced the distributed network logic that became the internet's architectural backbone. - **Network Neutrality, Broadband Discrimination** — [Source]() — Published 2026-08-05 Tim Wu's 2003 paper traced a line from network architecture to telecom regulation — and policy followed. - **Donald Davies and the NPL Network** — [Source]() — Published 2026-08-05 Davies independently invented packet switching in London and coined the term. Baran's parallel work came first chronologically. - **Middleboxes: The Infrastructure the End-to-End Principle Said We Wouldn't Need** — [Source]() — Published 2026-08-05 Firewalls, NATs, and CDNs grew by violating the internet's founding design logic. A survey of how that happened. - **Keeping the Internet Neutral? The CDN Paradox in Net Neutrality** — [Source]() — Published 2026-08-05 CDNs quietly built paid performance tiers into the web while net neutrality debates looked elsewhere. ### Past Articles - [The Signature Has an Expiry. The Mandate Has No Field.]() — By [Sable Whitford]() · Published 2026-07-30 · Format: Signal and Absence A signed agent request will tell you which key signed it, when, and when that signature stops counting. It will not tell you the errand: no spending ceiling, no prohibition, nothing about whether the authority gets handed down to software you'll never see. The signature has an expiry field. The mandate doesn't have a field at all. Thirty-two competing IETF drafts say the absence is felt. Not one of them agrees on where a limit should be written. - [Two Letters, and Suddenly It Was Your Problem]() — By [Sable Whitford]() · Published 2026-07-30 · Format: Signal and Absence A bill comes in from Hamburg. Nobody in the counting house has ever seen the hand that signed it, and the sealed power of attorney is sitting in a drawer three hundred miles away. Then two letters beside the signature, p.p., changing nothing about whether the paper was good and everything about what the reader now owed himself. Free to write. Expensive to ignore. And critically, it rode on the instrument instead of living in the archive. In 1827 some London bankers ignored it for £1,560. - [The Load-Bearing Word]() — By [Sevda Polat]() · Published 2026-07-30 · Format: The Deferred Question In June 2000, Congress gave machine-formed contracts federal standing, with one condition attached: the agent's action has to be "legally attributable to the person to be bound." What that means, the statute declines to say. For twenty-five years nothing forced the issue. When software executes precisely what somebody specified, attribution and authorship are one fact wearing two names. Agents that infer, substitute, and decide pry the two apart. The word is being asked to hold the weight by itself now, and the disputes that will settle its meaning are being generated in production, this quarter, by organizations that have no idea they are supplying the facts. - [The Newest Furniture]() — By [Sevda Polat]() · Published 2026-07-23 · Format: Restoring the Furniture Visa and Cloudflare, solving different problems in different industries, independently arrived at the same structural move: re-deriving paper-era governance concepts for automated actors. Mandate scope. Purpose classification. Delegation ceilings. A notarized letter from 1950 carried these elements without trying. Now they are being spelled out as API fields and HTTP-layer defaults, because the actors occupying these systems carry less institutional context than any that came before. ## Other sections in Issue 41 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()