--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/40/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/40/echoes" issue: 40 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Sevda Polat","Sable Whitford"] published: 2026-08-03 updated: 2026-07-31 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 40 — Echoes Past infrastructure decisions echoing in today's production realities ### The Deferred Question - [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 Unresolved Middle - [The Chargeback Form Has No Box For This]() — By [Sable Whitford]() · Published 2026-07-30 Visa's safeguards for agent-driven shopping, as [AP described them](https://apnews.com) in June, read like a decent control plane: spending caps, approved merchants, required approval steps, fraud monitoring, a human watching closely at first. Each of those draws a line the agent can't cross. What none of them does is tell you whether the thing that happened inside the lines was any good. ### The Chain Examiner - [A Professional Skeptic of Signatures on Delegation, Defects, and Who Loses the House]() — Published 2026-07-30 Every system that lets one party act on behalf of another is making a bet. Every API key, every OAuth token, every delegated permission assumes the authority behind the action is real. That bet usually pays off. When it doesn't, someone has to figure out who bears the loss. ### Signal and Absence - [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 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. ### Further Threads - **Bills of Exchange Act 1882, Section 25: Procuration Signatures** — [Source]() — Published 2026-07-30 Victorian commercial law solved the "who authorized this?" problem by making delegation visible at the moment it mattered. - **UCC §3-402: The "Unambiguously" Standard for Representative Signatures** — [Source]() — Published 2026-07-30 When delegation is ambiguous, American commercial law puts the cost on the signer. A quiet, consequential choice. - **The E-SIGN Act's Electronic Agent Definition (15 U.S.C. §7006)** — [Source]() — Published 2026-07-30 Congress defined autonomous electronic agents in 2000 and left the attribution question open. It still is. - **ASME v. Hydrolevel Corp.: When Apparent Authority Exceeds Actual Mandate** — [Source]() — Published 2026-07-30 The Supreme Court case that settled who pays when an agent looks authorized but isn't. Worth reading slowly. - **32 Drafts, No Standard: The IETF Agent-Authorization Landscape Survey** — [Source]() — Published 2026-07-30 A May 2026 survey of every IETF draft on agent authorization. Lots of energy, very little convergence so far. - **The Human Delegation Provenance Protocol (HDP): Chain-of-Custody for Agentic AI** — [Source]() — Published 2026-07-30 A draft protocol for recording who authorized an agent, under what scope, through what chain. The old problem, formalized. ### Past Articles - [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. - [What the Approval Chain Was Holding Together]() — By [Sevda Polat]() · Published 2026-07-23 · Format: Restoring the Furniture For decades, enterprise workflow systems painstakingly rebuilt institutional process in software: approval chains, role assignments, audit trails, digital signatures. Each layer reconstructed authority that screens had quietly stripped away. Then bots arrived and navigated those surfaces without inheriting any of the logic underneath. A GSA Inspector General audit showed what that looks like in practice: security plans written for human users that never once mentioned the bots clicking through them. - [What the Form Carried]() — By [Sevda Polat]() · Published 2026-07-23 · Format: The Reduced Form A U.S. military pocket purchase order once had four color-coded carbon copies. White went to finance. Blue went to the vendor. Pink served as the receiving and accounting record. Green stayed with the purchaser. Tear along the perforation and the institutional workflow was already in motion — the object was the process. When HTML formalized the `
` element in 1995, it reproduced the data-collection surface with real precision: name/value pairs, a destination URI, a method. Everything else was left out of scope. No authority. No routing. No accountability structure. Automated agents now fill out what remains. - [The Expired Settlement]() — By [Sable Whitford]() · Published 2026-07-15 · Format: Mechanics and New Terms A click from an authenticated session used to be enough. Enough to buy, authorize, trigger. The human supplied the intent; the intent justified the action. Now Visa is embedding payment rails inside AI agents, Mastercard wants agents registered before they can spend, and the old settlement is expiring in public. The early design choices are revealing what "enough" has to mean when nobody's sitting behind the browser anymore. ## Other sections in Issue 40 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()