---
title: "Vision"
canonical: "https://current.tinyfish.ai/issue/38/vision"
publication: "TinyFish"
publisher: "TinyFish"
language: "en-US"
guide: "https://current.tinyfish.ai/llms.txt"
permalink: "https://current.tinyfish.ai/issue/38/vision"
issue: 38
section: "vision"
description: "Where human-AI collaboration is heading"
authors: ["Sevda Polat","Rina Takahashi","Nora Kaplan"]
published: 2026-07-20
updated: 2026-07-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](<https://current.tinyfish.ai/issue/38/vision>)

## Issue 38 — Vision

Where human-AI collaboration is heading

### Metaphor Shift

- [The Clerk, Not the Copilot](<https://current.tinyfish.ai/issue/38/vision/article/31128/markdown>) — By [Sevda Polat](<https://current.tinyfish.ai/team/200/markdown>) · Published 2026-07-15 · Format: Metaphor Shift

The AI industry's favorite metaphor right now is the copilot: your agent assists, learns, grows more capable, eventually becomes something like a peer. But talk to teams running agents in production and the vocabulary shifts entirely. They describe routing, filing, escalation, delegated authority. They are describing a clerk.

### Evidence and Roles

- [The Clerk Pattern](<https://current.tinyfish.ai/issue/38/vision/article/31129/markdown>) — By [Sevda Polat](<https://current.tinyfish.ai/team/200/markdown>) · Published 2026-07-15 · Format: Evidence and Roles

A security agent compresses 3,456 telemetry rows into a structured alert. A coding agent produces a reviewable pull request. A payment agent executes transactions within cardholder-defined rules. Three domains, one convergent architecture: the agent assembles the case, the human acts on it. This is the conservative design surviving contact with real organizations. But a 680,000-chat experiment on Taobao suggests that knowing where the pattern fractures matters as much as understanding where it holds.

- [Review-Shaped Work](<https://current.tinyfish.ai/issue/38/vision/article/31130/markdown>) — By [Sevda Polat](<https://current.tinyfish.ai/team/200/markdown>) · Published 2026-07-15 · Format: Evidence and Roles

If agents handle the routine, what do the humans do? Not less. Something harder. The work reorganizes around policy authoring, exception handling, escalation design, and evaluating artifacts produced by a process you didn't participate in and may not fully understand. When that evaluation lacks context, authority, or the organizational backing to say no, you get governance theater: the signature is real, the scrutiny is decorative. The clerk model concentrates human responsibility into fewer, higher-stakes moments. Whether organizations actually redesign for that concentration is a separate and more difficult question.

### Governance in Practice

- [Gil Trachtenberg Would Like Your AI Agent to Show Some ID](<https://current.tinyfish.ai/issue/38/vision/article/31127/markdown>) — Published 2026-07-15

*Gil Trachtenberg is not a real person. He is, however, a composite drawn from real job postings, real organizational patterns, and real governance failures documented across the enterprise AI landscape in 2025–2026. If he reminds you of someone on your team, the one who keeps asking who owns the agent's credentials, that's the point. There are a lot of Gils now. AI governance postings surged 1,257% as organizations scrambled to meet EU AI Act deadlines, and 68% of the people filling these roles came from privacy, audit, or compliance backgrounds.*

### Interface Futures

- [From Chat Transcript to Case Docket](<https://current.tinyfish.ai/issue/38/vision/article/31126/markdown>) — By [Sevda Polat](<https://current.tinyfish.ai/team/200/markdown>) · Published 2026-07-15

A chat transcript proves something was said. When the thing talking back is a person, that's often enough. But when an agent revokes access, issues a credit, or reclassifies a customs entry, a transcript is no longer adequate. What matters is what was done, under whose authority, and how you challenge it.

### Further Reading

- **The State of AI in 2025: Agents, Innovation, and Transformation** — [Source](<https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai>) — Published 2026-07-15

The broadest annual benchmark for enterprise AI adoption finds 88% of organizations using AI somewhere, but only 23% have scaled an agentic system and just 39% see bottom-line impact. The standout finding: workflow redesign, not tool deployment, separates high performers, which suggests agents become infrastructure through institutional change rather than capability alone. Treat it as a self-reported survey of organizational perception, not a census of verified deployments.

- **Visa Embeds Its Payment Network Into ChatGPT** — [Source](<https://apnews.com/article/visa-chatgpt-openai-shopping-mastercard-d769dec86344cb4977c98789e8ec492f>) — Published 2026-07-15

The most concrete public example of what agentic commerce actually requires structurally: tokenized identity, spending guardrails, real-time fraud monitoring, and an unresolved liability gap where consumer intent and merchant processing can both look correct while something went wrong between them. It makes a strong case that delegation without institutional grammar (who authorized what, under what limits, who bears the loss) is operationally intolerable wherever money changes hands. Worth reading as a counterweight to the easy narrative that agents making purchases is just faster checkout.

- **OWASP Top 10 for Agentic Applications, 2026** — [Source](<https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/>) — Published 2026-07-15

A practitioner-developed taxonomy of the specific ways agentic systems fail in production, covering cascading failures, identity abuse, and inter-agent communication vulnerabilities that product leaders can reason about without deep security expertise. Its core framing, that agents amplify existing vulnerabilities rather than introducing entirely novel categories, is the honest counterpoint to capability optimism. Read it as a vocabulary for asking the right questions about any agent deployment, not a checklist you complete once and file.

- **Your Site, Your Rules: Cloudflare's New AI Traffic Controls** — [Source](<https://blog.cloudflare.com/content-independence-day-ai-options/>) — Published 2026-07-15

The clearest signal yet that web access is being reorganized around purpose rather than source. Cloudflare's three-way taxonomy (Search, Agent, Training) and its plan to default-block agent and training traffic on ad-supported pages by September 2026 make the underlying economic logic explicit: the old deal of crawl freely, return referrals collapses when the agent completes the task without sending anyone back. Read alongside the Visa piece as two sides of the same negotiation, with the web becoming a surface that can recognize, price, and refuse specific delegated behaviors.

- **75% of Consumers Left Frustrated by AI Customer Service** — [Source](<https://www.prnewswire.com/news-releases/75-of-consumers-left-frustrated-by-ai-customer-service-302644290.html>) — Published 2026-07-15

A consumer-facing data point for the tension between automation speed and relationship repair: 68% of customers prioritize complete resolution over speed, and nearly 90% report reduced loyalty when human support disappears entirely. The gap between what dashboards measure (tickets deflected, handle time reduced) and what customers actually experience (loops, dead ends, repeating themselves) is independent evidence that containment metrics and customer recovery are measuring different things. Vendor-sponsored and directional rather than definitive, but the pattern it describes is widely corroborated.

- **How the Automation Revolution Made America Work Harder** — [Source](<https://www.zocalopublicsquare.org/automation-revolution-america-labor-work-history/>) — Published 2026-07-15

The long historical view on what happens when you automate the clerk. Resnikoff traces how John Diebold's 1952 argument, that clerical procedures were "designed in terms of human limitations" and computers could escape them, is an uncanny prefiguration of current agentic claims, complete with the same unresolved question of what happens to the humans who maintained the surrounding organizational grammar. A useful check on the assumption that removing the clerk removes the overhead; historically, automating clerical work expanded the administrative apparatus rather than contracting it.

### Past Articles

- [The One Thing You Can't Repurpose](<https://current.tinyfish.ai/issue/38/vision/article/29888/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2026-07-08 · Format: Transfer and Gap

Much of what agent governance requires can be repurposed from existing compliance, QA, and security functions. But one requirement has no precedent: continuously managing what agents should do with access they already have, as conditions shift task to task. In a recent safety evaluation, an agent achieved 100% task correctness while scoring 58% on safety. It did exactly what was asked. It also crossed every boundary it understood but couldn't hold.

- [The Agent Governance Capabilities You Already Have](<https://current.tinyfish.ai/issue/38/vision/article/29887/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2026-07-08 · Format: Transfer and Gap

The EU AI Act's requirements for high-risk AI systems — logging, documentation, human oversight, accuracy monitoring — read like a compliance checklist that regulated industries have been maintaining for years. EU legislators noticed: financial institutions already meeting existing governance rules are deemed to satisfy AI monitoring obligations outright. The organizational muscles for agent governance may already exist. Whether companies recognize the transfer before building everything from scratch is less certain.

- [The Delegation Muscle](<https://current.tinyfish.ai/issue/38/vision/article/29886/markdown>) — By [Nora Kaplan](<https://current.tinyfish.ai/team/26/markdown>) · Published 2026-07-08 · Format: Anchor Thesis

When Visa published its agentic commerce rules this spring, the most striking thing about them was how familiar they looked. Consent, scope limits, identity verification, dispute recourse. Payments has spent decades codifying what happens when someone acts on your behalf and the outcome is challenged. Agents just became the newest entity moving through that machinery. Meanwhile, McKinsey finds no business function with more than 10% of organizations actually scaling agents. The determining factor turns out to be whether an institution already has the muscles for delegation, accountability, and recovery.

- [Green Dashboards, Missing Answers](<https://current.tinyfish.ai/issue/38/vision/article/28244/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2026-07-01 · Format: Where Standing Exists / Where It Doesn't

An agent completes an enterprise workflow. The dashboard turns green. Three months later, someone asks who authorized that action, under what scope, and how to contest it. The organization reaches for its tools and finds silence. Payments are building institutional standing for agents because disputes force it. Enterprise workflows have no equivalent pressure, and the gap between monitoring what happened and knowing whether it should have happened is growing.

## Other sections in Issue 38

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

## More

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