--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/45/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/45/echoes" issue: 45 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Sevda Polat","Sable Whitford"] published: 2026-09-07 updated: 2026-09-03 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 45 — Echoes Past infrastructure decisions echoing in today's production realities ### The Form Specification - [The Part of the Form That Stayed in the Office]() — By [Sevda Polat]() · Published 2026-09-03 · Format: The Form Specification When the HTML Working Group specified web forms in 1995, it translated the structure of paper forms with real fidelity: labeled fields, a destination, a method of delivery. What it did not translate was the institutional context that made paper forms work — who was authorized to fill one out, whether submitting it committed you to anything, what recourse you had when something went wrong. That context lived in the office, in the clerk, in the fine print on the back of the page. It was never encoded. Now automated agents are filling these same structures at scale, and the absence has started to matter. ### The Required Field - [What the Asterisk Stopped Asking]() — By [Sevda Polat]() · Published 2026-09-03 On a paper form, a blank required field started a conversation. The clerk noticed the gap, picked up the phone, asked what you meant. The asterisk marked where attention was needed, but the clerk supplied the judgment — deciding whether an answer was missing, wrong, or simply unclear. ### The Enrollment Specialist - [The Person Who Used to Stand Next to the Door]() — Published 2026-09-03 Open enrollment season at a large institution is a strange kind of deadline. For two or three weeks each November, tens of thousands of employees make decisions that will govern their healthcare, their tax-advantaged savings, and, in the case of beneficiary designations, the distribution of their assets after death. The portal that accepts these decisions validates field completeness and plan eligibility. It confirms that a selection was made. It does not confirm that the selection was understood. ### Two Lineages of Form Design - [What the Census Form Could See]() — By [Sevda Polat]() · Published 2026-09-03 · Format: Two Lineages of Form Design Before 2000, a census write-in of "Black-White" was assigned to Black. "White-Black" was assigned to White. The rule was consistent, defensible, and entirely invisible to the person it classified. Census categories determine which populations a country is equipped to perceive. A fifty-year-old design decision has finally been reversed. The statistical infrastructure it produced will outlast it by a decade. - [The Dropdown Menu]() — By [Sevda Polat]() · Published 2026-09-03 · Format: Two Lineages of Form Design Before the web dropdown, a clerk with a 30,000-entry index translated what you wrote into what the system could accept. The compression was lossy but intelligent — the clerk knew things about the world the index did not contain. The dropdown removed that interpreter. It worked partly because the humans on both sides understood what was being given up. What happens when the thing filling the form has no such understanding, and picks an option anyway? ### Further Reading on Forms - **How States Learn to See: James C. Scott on Standardization as Control** — [Source]() — Published 2026-09-03 Scott's foundational argument: forms are how institutions decide what exists and what doesn't. - **230 Years of Changing the Boxes: U.S. Census Race Categories Over Time** — [Source]() — Published 2026-09-03 Pew walks through every decade's racial categories, showing how the form kept rewriting the population. - **RFC 1866: The HTML Form Specification That Left Authority Out** — [Source]() — Published 2026-09-03 The 1995 spec defined web forms as name/value pairs and never once addressed who was filling them in. - **The Law That Tried to Kill Paperwork and Made More of It** — [Source]() — Published 2026-09-03 The Paperwork Reduction Act meant well, then got stuck on a 1949 definition and multiplied what it aimed to cut. - **Census Categories as Political Architecture** — [Source]() — Published 2026-09-03 Hochschild and Powell trace how racial classifications on census forms helped construct the social order they claimed to describe. - **Forms as Conversations: Luke Wroblewski's Case for Designing Around the Human** — [Source]() — Published 2026-09-03 The 2008 practitioner guide that reframed form design as dialogue with a person, written before agents complicated the picture. ### Past Articles - [What an API Costs to Keep Open]() — By [Sevda Polat]() · Published 2026-08-28 · Format: Two Attempts at Resolution If RSS was too simple to sustain universal coverage, APIs offered the opposite bet: structured, authenticated, richly documented interfaces between machines. By 2018, directories tracked over 19,000 of them. But each one is a commitment the provider has to keep renewing — versioned, supported, and eventually restricted when it costs more than it returns. Reddit's API still worked the day Apollo shut down. What changed was the price of using it. - [What RSS Couldn't Make Free Enough]() — By [Sevda Polat]() · Published 2026-08-28 · Format: Two Attempts at Resolution RSS asked almost nothing of publishers: a small XML file, no authentication, no negotiation. By 2008, half of consumer-media sites offered feeds. It was the lowest-cost path to universal machine-readable access anyone had tried. Then Twitter pulled its feeds, Google shut down Reader, and the platforms that controlled distribution stopped maintaining the side door. Even a cost that small was still a cost someone had to keep paying. - [The Workaround Is the Pattern]() — By [Sevda Polat]() · Published 2026-08-28 · Format: Integration's Permanent Oscillation In 1984, IBM shipped a tool that let programs read a mainframe terminal screen character by character, pretending to be a human operator. It was fragile but immediately useful, because the cooperative alternative required both sides to agree, and agreement has costs that sort participants. Organizations that can afford structured integration get it; everyone else builds a workaround. Forty years later, AI agents are filling out web forms and clicking buttons for the same structural reason. The pattern predates the web. - [Records Nobody Reads Until Something Breaks]() — By [Sable Whitford]() · Published 2026-08-20 · Format: Two Ledgers In 1983 a C program called syslog started appending timestamped lines to a file. It didn't check order, completeness, or who sent what, because the reader was assumed to be an engineer arriving after a crash. That append-everything, search-later model became the default shape of digital record-keeping. Agent audit trails are inheriting it now, and pointing it at a question it was never built for: not what broke, but what a system decided and whether it had the authority to decide it. ## Other sections in Issue 45 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()