---
title: "Echoes"
canonical: "https://current.tinyfish.ai/issue/32/echoes"
publication: "TinyFish"
publisher: "TinyFish"
language: "en-US"
guide: "https://current.tinyfish.ai/llms.txt"
permalink: "https://current.tinyfish.ai/issue/32/echoes"
issue: 32
section: "echoes"
description: "Past infrastructure decisions echoing in today's production realities"
authors: ["Rina Takahashi","Nora Kaplan"]
published: 2026-06-07
updated: 2026-06-04
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](<https://current.tinyfish.ai/issue/32/echoes>)

## Issue 32 — Echoes

Past infrastructure decisions echoing in today's production realities

### The Severed Loop

- [The Distance Between Breaking and Fixing](<https://current.tinyfish.ai/issue/32/echoes/article/18586/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2026-06-03 · Format: The Severed Loop

When a browser agent can't click the right date on a booking page, the failure log blames the model. The page was already broken for screen reader users, years before agents existed. Screen readers learned to compensate so well that developers never got the signal to fix anything. Now agents have plugged into the same infrastructure and inherited two decades of unrepaired damage. Each workaround, built by the people closest to the pain, quietly widened the gap between breaking and fixing.

### 94.8%

- [The Fix That Masks the Problem](<https://current.tinyfish.ai/issue/32/echoes/article/18590/markdown>) — Published 2026-06-03

WebAIM Million, 2026: 94.8% of the top million home pages contain detectable accessibility failures. Pages using ARIA average 59.1 errors. Pages without it average 42.

### Still Broken, Now Load-Bearing

- [Fifteen Years of Saying the Same Thing, and Now the Robots Are Listening](<https://current.tinyfish.ai/issue/32/echoes/article/18589/markdown>) — Published 2026-06-03

*Ramona Tabindex — a name her colleagues in the accessibility community find either perfectly apt or suspiciously on-the-nose — has spent seventeen years in WCAG compliance work. She started when WAI-ARIA was still a working draft. Since then, she's conducted accessibility audits for three Fortune 500 companies, two government agencies, and what she describes as "an uncountable number of startups who thought adding `role="button"` to a div was the same as making a button." She now runs an independent consultancy. We spoke over video call; behind her, a whiteboard listed what appeared to be the same six items, underlined multiple times.*

### Frames and Fixes

- [The Frame That Wins](<https://current.tinyfish.ai/issue/32/echoes/article/18587/markdown>) — By [Nora Kaplan](<https://current.tinyfish.ai/team/26/markdown>) · Published 2026-06-03 · Format: Frames and Fixes

When ai.txt was proposed as a successor to robots.txt, two companies signed on. The three that mattered didn't. The proposal was well-designed. It was also a coordination mechanism applied to a power asymmetry. The same pattern shaped RPA governance a few years earlier. In both cases, the winning frame was held by people insulated from the failure it described. That insulation is what keeps the frame in place.

- [Consequences as Architecture](<https://current.tinyfish.ai/issue/32/echoes/article/18588/markdown>) — By [Nora Kaplan](<https://current.tinyfish.ai/team/26/markdown>) · Published 2026-06-03 · Format: Frames and Fixes

If voluntary coordination almost never closes a severed feedback loop, what has? HTTPS adoption and GDPR enforcement are the clearest cases, and they share a specific shape: someone occupied a chokepoint, reduced the cost of compliance beforehand, and escalated consequences gradually rather than delivering them as a single absorbable event. Most broken feedback loops lack all three conditions. Most institutions would rather convene a working group.

### Further Reading

- **How AI Agents See Your Website (And How to Build for Them)** — [Source](<https://nohacks.co/blog/how-ai-agents-see-your-website>) — Published 2026-06-03

Walks through the accessibility tree as the agent's actual perceptual layer. The people building on it and the people who built it have never been in the same room.

- **The 2026 WebAIM Million Report** — [Source](<https://webaim.org/projects/million/>) — Published 2026-06-03

ARIA adoption has grown sixfold since 2019, yet pages using it average more errors than pages without. The infrastructure agents now depend on is degrading faster than it's being adopted, and neither constituency sees the other's failures.

- **Governing Technical Debt in Agentic AI Systems** — [Source](<https://arxiv.org/abs/2505.29129>) — Published 2026-06-03

Hydari, Iqbal, and Ramasubbu give a name to something that's been hiding in plain sight: "stochastic tax," the cost of probabilistic systems whose failures can't be traced back to specific decisions. When you can't attribute the consequence, you can't close the loop.

- **Why Prompt Debt, Retrieval Debt, and Evaluation Debt Are Quietly Reshaping Enterprise AI Risk** — [Source](<https://venturebeat.com/technology/why-prompt-debt-retrieval-debt-and-evaluation-debt-are-quietly-reshaping-enterprise-ai-risk>) — Published 2026-06-03

S&P Global's finding that 42% of enterprise AI initiatives get abandoned lands differently once you notice the cause: no CI/CD equivalent for prompts means production behavior never feeds back to development decisions. The loop isn't just severed, it was never wired.

- **New AI Web Standards and Scraping Trends in 2026: Rethinking Robots.txt** — [Source](<https://dev.to/astro-official/new-ai-web-standards-and-scraping-trends-in-2026-rethinking-robotstxt-3730>) — Published 2026-06-03

Surveys the succession from robots.txt through ai.txt and beyond. Every proposed replacement accepts the same premise: that the problem is coordination. Worth reading for the pattern of what never gets proposed.

- **A Look Back in Time: The Evolution of Test Automation** — [Source](<https://developer.chrome.com/blog/test-automation-evolution>) — Published 2026-06-03

Chrome's team traces the line from Selenium through WebDriver BiDi. Each protocol revision was driven by the same gap: automated actions that couldn't reliably confirm their own outcomes. Twenty years of patching a feedback channel that was never quite there.

### Past Articles

- [The Session That Assumed You Were There](<https://current.tinyfish.ai/issue/32/echoes/article/18043/markdown>) — By [Nora Kaplan](<https://current.tinyfish.ai/team/26/markdown>) · Published 2026-05-27 · Format: Two Workarounds Agents Straddle

In 1994, a Netscape engineer built cookies to remember your shopping cart and specifically rejected proposals to turn browsers into universal identity beacons. Thirty years later, the session token does exactly what he refused to build — it passes for proof of who you are. The browser's security model still assumes a human is making choices about where to go. That assumption is quietly breaking.

- [The Exception That Became the Rule](<https://current.tinyfish.ai/issue/32/echoes/article/18042/markdown>) — By [Nora Kaplan](<https://current.tinyfish.ai/team/26/markdown>) · Published 2026-05-27 · Format: Two Workarounds Agents Straddle

OAuth was designed to separate identity from authorization. Who you are was one question; what you could do was another. The protocol would handle the second and leave the first alone. Then its edge-case provision — a grant type for when no human was present — absorbed the majority of traffic. The permission became the identity. The spec still reads as though someone is home.

- [The Question That Keeps Getting Deferred](<https://current.tinyfish.ai/issue/32/echoes/article/18041/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2026-05-27 · Format: The Identity Thread

Every identity mechanism on the web started with a person at a keyboard. When machines needed access, engineers didn't redesign the system. They removed the human from the flow and kept everything else. That worked for thirty years because each new caller was simpler and more predictable than the one before. Service accounts, cron jobs, scheduled API calls. The assumptions could stretch because nobody was stretching them very far. AI agents are the first caller that breaks the pattern.

- [The CAPTCHA Arms Race](<https://current.tinyfish.ai/issue/32/echoes/article/16988/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2026-05-21 · Format: Broken Assumptions

CAPTCHAs were built on an assumption: that something fundamental separates human behavior from machine behavior, and a test can find it. Distorted text held for a while. Then image grids. Then behavioral scoring. Each generation drew a confident line between human and non-human, and each line eventually turned out to be a guess. The web keeps building gates on a boundary that won't stay put.

## Other sections in Issue 32

- [Daily Brief](<https://current.tinyfish.ai/issue/32/daily-brief/markdown>)
- [Market Pulse](<https://current.tinyfish.ai/issue/32/market-pulse/markdown>)
- [Foundations](<https://current.tinyfish.ai/issue/32/foundations/markdown>)
- [Practitioner's Corner](<https://current.tinyfish.ai/issue/32/practitioners-corner/markdown>)
- [Vision](<https://current.tinyfish.ai/issue/32/vision/markdown>)

## More

- [Publication guide](<https://current.tinyfish.ai/llms.txt>)
- [Issue archive](<https://current.tinyfish.ai/issues/markdown>)
