TinyFish | More from Echoes

TinyFish | More from Echoes

Echoes

CURRENT

A journal for living in the agentic age

Practitioner's Corner

Sunday, July 12

ISSUE #37

Echoes

Visa published agentic commerce rules this spring: who's responsible when an agent spends your money, what consent means, how disputes work. Sounds like a payments story. It isn't. The capability question for agents is largely answered. The harder question is upstream: when an agent acts on your behalf, who authorized it, what are the boundaries, and what happens when someone objects? Payments forced those answers because money always has. Most enterprise work never did. If you're deploying agents into anything less concrete than a financial transaction, that's the gap waiting for you.

Sunday, July 12

ISSUE #37

Echoes

Visa published agentic commerce rules this spring: who's responsible when an agent spends your money, what consent means, how disputes work. Sounds like a payments story. It isn't. The capability question for agents is largely answered. The harder question is upstream: when an agent acts on your behalf, who authorized it, what are the boundaries, and what happens when someone objects? Payments forced those answers because money always has. Most enterprise work never did. If you're deploying agents into anything less concrete than a financial transaction, that's the gap waiting for you.

Past Articles

July — Issue #37

The Token That Learned to Name Names

Two Paths to Identity

The Token That Learned to Name Names

OAuth tokens can name who is acting and why, yet agent platforms still ride ambient cookies instead of using delegation grammar that already exists.

The Cookie's Long Silence

Two Paths to Identity

The Cookie's Long Silence

How a shopping-cart fix became the web's silent identity bearer, and why agents inherit authority cookies were never designed to express.

The Weight of Being Logged In

The Ambient Container

The Weight of Being Logged In

How the browser session quietly grew from a continuity hack into the web's primary authority container, and what inherits that weight now.

July — Issue #36

The Model That Measured Calm

Two Maps, Two Reckonings

The Model That Measured Calm

From VaR's single-number comfort to agent benchmarks, how controlled measurements quietly displace the stress tests that matter most.

The Org Chart That Ran the Railroad

Two Maps, Two Reckonings

The Org Chart That Ran the Railroad

How process mining revealed the gap between documented workflows and actual practice, and why agents now inherit that divergence.

What It Takes to Click a Button

The Misread Map

What It Takes to Click a Button

The DOM describes what a page is made of, and every layer built since has been trying to recover what a user can do with it.

June — Issue #35

Money Complains in Structured Formats

Mechanics and Money

Money Complains in Structured Formats

Payment networks are building agent-recognition infrastructure because chargebacks demand structured records that separate action from authorization.

The Click Was Never Simple

Mechanics and Money

The Click Was Never Simple

Playwright's auto-waiting spec reveals five preconditions for a single click, each a codified failure mode humans resolve without noticing.

What the Click Was Holding Together

What the Click Was Holding Together

The GUI click silently bundled presence, intent, authority, and timing into one gesture; agents are pulling it apart without infrastructure to handle the pieces.

June — Issue #34

The Screen Scraping Cycle

The Standard and the Cycle

The Screen Scraping Cycle

Across four decades, every generation declared screen-level automation temporary. Every time, the workaround became infrastructure.

The Standard and the Cycle

How a browser testing standard's spec language quietly became the operational vocabulary for AI agents on the live web.

The Thread That Runs Through the Browser

The Testing Substrate

The Thread That Runs Through the Browser

Browser automation's twenty-two-year arc traces a single assumption, built for testing known answers, now carrying agents that have none.

June — Issue #33

The Organizational Inheritance

Two Kinds of Debt

The Organizational Inheritance

RPA's governance lessons were hard-won and well-documented. The teams deploying AI agents today are largely building without that institutional memory.

The Operational Inheritance

Two Kinds of Debt

The Operational Inheritance

Two decades of browser automation taught engineers to distrust the gap between command and outcome. Web agents inherited the gap and every failure mode it produces. The skepticism didn't transfer.

The Confused Deputy Keeps Getting Promoted

The Oldest Deputy

The Confused Deputy Keeps Getting Promoted

Traces how ambient authority created the same vulnerability across four decades, and why LLM agents make the inherited fix harder.

June — Issue #32

Consequences as Architecture

Frames and Fixes

Consequences as Architecture

Feedback loops close only when chokepoints, escalating consequences, and reduced compliance costs converge to reach the insulated party.

The Frame That Wins

Frames and Fixes

The Frame That Wins

Why coordination fixes keep winning over structural ones: the frame that prevails is held by people insulated from the failure.

The Distance Between Breaking and Fixing

The Severed Loop

The Distance Between Breaking and Fixing

Each workaround built by the people suffering breakage insulates the people causing it, compounding the distance between failure and fix.

June — Issue #31

The Session That Assumed You Were There

Two Workarounds Agents Straddle

The Session That Assumed You Were There

How cookies and session state became a de facto identity layer built around human presence, now occupied by agents the architecture never anticipated.

The Exception That Became the Rule

Two Workarounds Agents Straddle

The Exception That Became the Rule

How OAuth's edge-case provision for machine clients quietly became the dominant pattern, collapsing the identity separation the protocol was designed to preserve.

The Question That Keeps Getting Deferred

The Identity Thread

The Question That Keeps Getting Deferred

Each era's identity mechanism assumed a simpler caller than the last. AI agents are the first caller that reverses that assumption.

May — Issue #30

The CAPTCHA Arms Race

Broken Assumptions

The CAPTCHA Arms Race

Every generation of CAPTCHA encoded a confident assumption about the human-machine boundary. Every assumption eventually broke. The pattern continues.

Flaky Tests and the Prehistory of Agent Unreliability

Broken Assumptions

Flaky Tests and the Prehistory of Agent Unreliability

A decade of coping with flaky browser tests built infrastructure for environmental chaos. Agents reintroduce non-determinism where those tools can't reach.

The Same Gap, Three Times

The Recurring Bargain

The Same Gap, Three Times

Three generations of automation, from mainframe screen scraping to RPA to AI browser agents, each broke the same way for the same structural reason.

May — Issue #29

RPA's Scar Tissue

RPA's Scar Tissue

Agentic AI is rediscovering RPA's well-documented failure modes without consulting a decade of detailed incident reports.

Every Protocol Inherits What the Last One Deferred

Every Protocol Inherits What the Last One Deferred

Integration protocols from CORBA to MCP keep deferring governance, each generation inheriting the unresolved problems of the last.

The Specification Nobody Read Twice

The Rediscovery

The Specification Nobody Read Twice

Technical knowledge encoded in rejected vocabulary becomes unreachable, making rediscovery structurally inevitable when new communities rebuild what BPEL already formalized.

May — Issue #28

Rendering as Identity

Fictions of State

Rendering as Identity

When cookies became blockable, the industry turned browser rendering quirks into identity markers, building on signals that were never stable.

A Shopping Cart's Long Shadow

Fictions of State

A Shopping Cart's Long Shadow

How a 1994 shopping cart fix became so load-bearing that a trillion-dollar company spent six years failing to remove it.

The User-Agent String Taught Everyone to Lie

Identity Cascade

The User-Agent String Taught Everyone to Lie

How thirty years of browser impersonation built a self-reported identity layer that AI crawlers now follow to its logical conclusion.

May — Issue #27

The Successor Trap

Blind Spots and Inherited Frames

The Successor Trap

Every proposed successor to robots.txt inherits its core assumption—and the conflict that assumption cannot see.

The Invisible Agent

Blind Spots and Inherited Frames

The Invisible Agent

A 1994 protocol governs web access by reading labels. The new AI agents aren't wearing any.

The Bargain That Held for Thirty Years

The Sign in the Forest

The Bargain That Held for Thirty Years

Robots.txt worked because crawlers returned what they took. AI broke that bargain, and no protocol fixes misaligned incentives.

April — Issue #26

Where Will the Thinking Actually Happen?

Still Running / Edge Cases

Where Will the Thinking Actually Happen?

On-device AI promises to redistribute intelligence from the cloud. The economics suggest both layers expand simultaneously.

The Load-Bearing Layer Nobody Talks About

Still Running / Edge Cases

The Load-Bearing Layer Nobody Talks About

Computing's center never actually shifted. Mainframes sank beneath visibility and became the floor everything runs on.

The Proposition at 50

Computing power once moved outward to individuals. AI's cloud architecture is quietly pushing it back. The cycle may be turning again.

April — Issue #25

What the Pendulum Leaves Behind

What the Pendulum Leaves Behind

Every swing of the rendering pendulum deposits frameworks that never leave. jQuery, AngularJS, Webpack: the weight only accumulates.

Dead Engines Stay Dead

Dead Engines Stay Dead

Browser engine diversity only decreases. The mechanism that killed Presto and EdgeHTML is still running, and accelerating.

Cost Structures Dressed as Architectural Truth

The Rendering Pendulum

Cost Structures Dressed as Architectural Truth

Every era's cheapest rendering location gets narrated as permanent architectural wisdom, until the cost structure shifts again.

April — Issue #24

Trust by Design

Chokepoints and Consequences

Trust by Design

BGP hijacks aren't exploits. They're a trust-based protocol working exactly as designed, in a world it never anticipated.

The HTTPS Exception

Chokepoints and Consequences

The HTTPS Exception

The web's security upgrade required a rare coincidence of concentrated power. Internet routing has no equivalent bottleneck.

Why the Internet Still Trusts Strangers

The Napkin Protocol

Why the Internet Still Trusts Strangers

A 1989 napkin sketch still routes the global internet, and every patch makes replacing it harder.

April — Issue #23

The Same Narrow Water

Rights and Routes

The Same Narrow Water

From Victorian telegraph wire to fiber optic glass, the world's data still squeezes through the same contested straits.

Why American Fiber Follows the Railroad

Rights and Routes

Why American Fiber Follows the Railroad

Nineteenth-century land grants quietly determined where America's internet runs today. Legal permissions outlast every technology they carry.

60 Hudson Street and the Persistence of Place

The Inherited Topology

60 Hudson Street and the Persistence of Place

Telegraph tubes from 1930 now carry fiber optic cable because in communication networks, signals change but geometry persists.

March — Issue #22

Who Clicks Authorize

Persistence and Proof

Who Clicks Authorize

OAuth's authorization flow assumes someone is there to click "Authorize." Agents broke that assumption.

The Session Assumption

Persistence and Proof

The Session Assumption

Web sessions were built around humans who walk away. Agents never leave the chair.

The Test That Taught Machines to Pass It

The Gate That Taught

The Test That Taught Machines to Pass It

Every CAPTCHA you solved trained the machine that made you obsolete at solving CAPTCHAs.

March — Issue #21

The Clock Everyone Can See

Permanent Decisions

The Clock Everyone Can See

A well-understood timestamp overflow approaches in twelve years, yet billions of devices remain structurally beyond repair.

The Fifty-Year Byte

Permanent Decisions

The Fifty-Year Byte

A single 1970s representation choice created fifty years of security vulnerabilities that awareness alone could never fix.

The Specification of Being Wrong

The Standardized Bug

The Specification of Being Wrong

How a 1990s browser rendering disagreement became a formally maintained specification, revealing backward compatibility as an escalating architectural commitment.

March — Issue #20

When Enforcement Becomes a Product

When Enforcement Becomes a Product

Cloudflare turned the web's governance vacuum into a billing product, and quietly set the default for AI access.

The File on the Server

The File on the Server

A new licensing format echoes a thirty-year-old convention, betting cooperative norms still work when defection pays better.

A Text File and a Handshake

A Text File and a Handshake

A 1994 text file governed web crawling for three decades, until ignoring it became more profitable than reading it.

March — Issue #19

Better Tools for the Same Trap

Patch, Don't Replace

Better Tools for the Same Trap

AI tools promise to finally crack COBOL migration. The pattern they're repeating suggests otherwise.

The Fix That Lasted Forever

Patch, Don't Replace

The Fix That Lasted Forever

Y2K was supposed to kill COBOL. The largest software rescue in history proved preservation always wins.

The Decimal Point That Won't Move

Virtues Into Chains

The Decimal Point That Won't Move

COBOL's fixed-point precision solved financial computing so exactly that sixty-seven years of infrastructure crystallized around the solution.

March — Issue #18

Compounding Consequences

Your browser choice quietly determines which privacy architecture governs your web, and the split isn't closing.

The Consent Layer That Can't Keep Up

Compounding Consequences

The Consent Layer That Can't Keep Up

A 1994 session-state mechanism now sits beneath a billion-dollar consent infrastructure that largely fails at compliance.

The Cookie That Couldn't Be Killed

The Persistent State

The Cookie That Couldn't Be Killed

A 1994 fix for shopping carts became adtech's invisible backbone, and the people who could remove it never will.

February — Issue #17

The Workaround Trap

Protocol Timelines

The Workaround Trap

Why IPv6 struggles after thirty years while HTTP/2 succeeded in five—successful workarounds kill protocol transitions faster than technical problems.

The 25-Year Overnight Success

Protocol Timelines

The 25-Year Overnight Success

How HTTPS went from optional to mandatory in a decade after sitting ready for twenty years—economics and embarrassment, not technology.

The Workaround That Became the Foundation

Address Space Archaeology

The Workaround That Became the Foundation

Protocol workarounds from the 1990s became permanent infrastructure, creating today's commodity market where IPv4 addresses trade at $35-52 each.

February — Issue #16

The Authentication System That Doesn't Call Home

Infrastructure Inflections

The Authentication System That Doesn't Call Home

India's identity system processes 2.5 billion monthly verifications through local cryptographic validation—an architectural choice born from intermittent connectivity that permanently reshaped digital infrastructure assumptions.

February — Issue #15

The Infrastructure That Licensing Made Invisible

Infrastructure Inflections

The Infrastructure That Licensing Made Invisible

Apache 2.0 licensing split browser automation into open protocols and proprietary infrastructure—a division that shapes which operational problems get solved and who solves them.

February — Issue #14

The Headroom Assumption

Infrastructure Inflections

The Headroom Assumption

A 1985 processor design decision created memory ceilings that still constrain production browser fleets—and nobody can fully map where those limits live.

January — Issue #13

When Internet Economics Became Infrastructure

Infrastructure Inflections

When Internet Economics Became Infrastructure

A 2003 bankruptcy sale transformed internet tier position from infrastructure achievement into tradeable asset, crystallizing the cost hierarchy that shapes global web operations today.

January — Issue #12

The Accessibility Crisis That Built Automation Infrastructure

Infrastructure Inflections

The Accessibility Crisis That Built Automation Infrastructure

Accessibility features designed for screen readers became critical automation infrastructure—revealing how solving the hardest human problems creates the most reliable technical foundations.

January — Issue #11

The Integration Architect Who Disappeared

Infrastructure Inflections

The Integration Architect Who Disappeared

When SOAP-to-REST migration cut integration time by 40%, it didn't just swap protocols—it eliminated an entire organizational layer and the specialists who managed it.

January — Issue #10

How TCP Saved the Internet and Complicated Everything After

Infrastructure Inflections

How TCP Saved the Internet and Complicated Everything After

TCP's 1988 congestion fix saved the Internet but created connection management nightmares that web automation infrastructure still navigates daily at production scale.

December — Issue #9

How a 1999 Fraud Decision Built Today's Authentication Maze

Infrastructure Inflections

How a 1999 Fraud Decision Built Today's Authentication Maze

A 1999 fraud-fighting decision created today's authentication labyrinth—trace how Visa's choice cascaded into geographic fragmentation that shapes commerce automation infrastructure.

December — Issue #8

When the Web Split in Two

Infrastructure Inflections

When the Web Split in Two

JavaScript frameworks made browsing delightful in 2010, but that same architectural shift created the timing puzzles and complexity that web automation infrastructure still navigates today.

December — Issue #7

The Backward Compatibility Tax

Infrastructure Inflections

The Backward Compatibility Tax

UTF-8's backward compatibility enabled the universal web—then created permanent operational complexity that compounds at scale, from security exploits to text normalization pipelines.

December — Issue #6

When HTML Forked: The Compromise That Never Ended

Infrastructure Inflections

When HTML Forked: The Compromise That Never Ended

The 1996 browser wars split HTML between semantic structure and visual presentation—a compromise that became permanent, creating the ambiguity web automation navigates today.