--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/47/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/47/echoes" issue: 47 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Sevda Polat","Sable Whitford"] published: 2026-09-21 updated: 2026-09-17 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 47 — Echoes Past infrastructure decisions echoing in today's production realities ### Conservation Framework - [What Stays Behind]() — By [Sevda Polat]() · Published 2026-09-17 · Format: Conservation Framework In 1987, a conservation scientist soaked treated ceramics in solvent for eight hours. Roughly half the resin stayed behind. The treatment was considered reversible. Barbara Appelbaum argued that her profession needed a better question than whether something could be undone, and proposed asking instead what any intervention leaves available to whoever has to work on the object next. Nearly four decades later, the W3C is working out when software agents should be allowed to commit users to transactions they cannot fully reverse — arriving at the same problem, apparently without knowing it had already been formalized. ### Atomicity Sidebar - [When Rollback Stopped Meaning Undo]() — By [Sable Whitford]() · Published 2026-09-17 Inside a single database, rolling back a transaction is erasure. The writes vanish, the locks release, the data looks exactly as if you'd never tried. Jim Gray described this in 1981: a transaction transforms state atomically, or it doesn't. Härder and Reuter named the properties ACID in 1983, and for a generation of engineers, "rollback" meant the system handled it. ### Residue Consultant - [Fifty Percent Still There — A Museum Conservator Looks Inside the Undo Button]() — Published 2026-09-17 *Perpetua Dross is, by her own description, "a person who spends Mondays through Wednesdays worrying about adhesive migration in eighteenth-century ceramics and Thursdays through Fridays worrying about whether anyone at a payments company has ever heard the word 're-treatability.'" She is a Professional Member of the American Institute for Conservation, an objects conservator with two decades of experience at university museums, and since early 2025, a consultant for a mid-size fintech firm that asked her to help design what they call "intervention frameworks" for automated transaction handling.* ### Never Erase - [The Ledger That Never Forgets]() — By [Sevda Polat]() · Published 2026-09-17 · Format: Never Erase In 1494, a Franciscan friar wrote down what to do when you post the wrong number: don't erase it. Add a second entry explaining the mistake, then record the correction. Three entries where one scratch-out would do. Venetian merchants had already settled on the slower method, and eventually federal law agreed with them. The wrong entry still belongs in the book. Any system that overwrites what was there before faces the question they answered. - [The Chart That Cannot Be Unwritten]() — By [Sevda Polat]() · Published 2026-09-17 · Format: Never Erase A chiropractor recopied a patient's chart after a malpractice complaint arrived. The rewritten version described a patient who had improved and was satisfied. The original, which the patient happened to have copied, described neither. Healthcare learned case by case, and expensively, that altering a clinical record does more than revise the past. It cuts the reasoning out from under decisions other people already made on the strength of it. ### Further Reading - **Criteria for Treatment: Reversibility** — [Source]() — Published 2026-09-17 Appelbaum's 1987 paper showed that reversibility in conservation is always partial — residue persists after every treatment. - **Sagas** — [Source]() — Published 2026-09-17 Garcia-Molina and Salem defined compensation as "acceptable approximation" in 1987 — a subtlety most implementations still miss. - **Paper Summary: Sagas** — [Source]() — Published 2026-09-17 Tornow's walkthrough of the original saga paper draws out the compensation semantics that modern frameworks tend to flatten. - **IAS 8 — Basis of Preparation of Financial Statements** — [Source]() — Published 2026-09-17 The IFRS standard requiring material errors to be corrected by restating prior periods — the past gets rewritten, not patched. - **EHR Audit Trail: Complete Guide to Electronic Health Record Tracking** — [Source]() — Published 2026-09-17 Covers the Prieto ruling, which reclassified audit logs from operational telemetry to part of the patient's designated record set. - **Understanding EMR Audit Trails: Importance and Implications for Medical Record Alteration** — [Source]() — Published 2026-09-17 A legal perspective on why clinical records can be amended but never erased — original entries must stay visible alongside corrections. ### Past Articles - [The Deputy Who Couldn't Tell Its Authorities Apart]() — By [Sable Whitford]() · Published 2026-09-10 · Format: Competing Lineages A 1960s proposal held that authority should travel with each request rather than pool under the caller's identity. It lost to identity-based access control — the model the companion piece traces. Then a compiler destroyed a billing file because the operating system couldn't tell the compiler's own permissions apart from its user's, and that failure got a name: the confused deputy. Agent systems are now rediscovering what capability-based security proposed before Unix existed. - [The User Who Was Always a Person]() — By [Sable Whitford]() · Published 2026-09-10 · Format: Competing Lineages Unix's permission model was built for people at terminals in 1974. It answered "what may this code do?" by asking "who is running it?" Those same permission bits, checked against a user identity, now enforce container isolation for autonomous agents — processes holding credentials with no person behind them. Identity was always standing in for the mandate. Agents are the first users where that substitution stops working. - [The Sandbox That Couldn't Hold]() — By [Sable Whitford]() · Published 2026-09-10 · Format: Containment Precedent In 1995, Sun Microsystems shipped the Java applet sandbox to answer a question the industry is answering again: how do you let code you didn't write run autonomously inside bounds you control? The sandbox was carefully built, enforced in multiple layers, by people who understood what remote code might try. It came apart anyway — not because attackers broke through, but because its own designers kept loosening it so the code could get anything done. Browsers eventually deleted applet support rather than fix it. The specific mechanics of that erosion are recognizable in agent containment right now. - [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? ## Other sections in Issue 47 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()