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

## Issue 37 — Vision

Where human-AI collaboration is heading

### Anchor Thesis

- [The Delegation Muscle](<https://current.tinyfish.ai/issue/37/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.

### Transfer and Gap

- [The Agent Governance Capabilities You Already Have](<https://current.tinyfish.ai/issue/37/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 One Thing You Can't Repurpose](<https://current.tinyfish.ai/issue/37/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.

### Ground-Level View

- [Thirty Years of Regulatory Resentment Turned Out to Be Agent Infrastructure](<https://current.tinyfish.ai/issue/37/vision/article/29885/markdown>) — Published 2026-07-08

*Deb Fortunato is VP of Claims Operations at a mid-size property and casualty carrier in the Midwest. Or she would be, if she existed. She's a composite: built from interviews with claims leaders, industry surveys, regulatory filings, and the operational realities of a domain where every decision might end up in a deposition. Her opinions are grounded in real data and real tensions. Her name is her own.*

### Provocation Sidebar

- [The Plumbing of Suspicion](<https://current.tinyfish.ai/issue/37/vision/article/29884/markdown>) — By [Nora Kaplan](<https://current.tinyfish.ai/team/26/markdown>) · Published 2026-07-08

The organizations moving fastest on agent deployment in regulated finance tend to share a trait that has nothing to do with their AI teams. They already had separation of duties threaded through every transaction. Initiator separated from approver separated from recorder, each action logged, each credential scoped, each exception routed to review.

### 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-08

The sharpest current data on how wide AI adoption has gotten and how shallow agent deployment remains. The workflow-redesign findings alone are worth your time.

- **Visa Plugs Its Payment Network into ChatGPT** — [Source](<https://apnews.com/article/d769dec86344cb4977c98789e8ec492f>) — Published 2026-07-08

AP's reporting on spending limits, safeguards, and the genuinely unresolved middle cases when an agent buys something you sort of wanted. The best narrative window into agentic commerce's real friction.

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

Security thinking that finally catches up to what agents actually do. The threat model here centers on systems that plan and act across workflows, not just models that generate text.

- **An Evaluation of Data Leakage Risks in Tool-Using LLM Agents in Realistic Scenarios** — [Source](<https://arxiv.org/abs/2606.17114>) — Published 2026-07-08

A joint safety-institute evaluation with a finding that should unsettle anyone shipping agents: tasks completed correctly while data leaked out the side. Capability and institutional readiness are different problems.

- **Visa Core Rules and Visa Product and Service Rules, April 2026** — [Source](<https://usa.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf>) — Published 2026-07-08

Dense reading, but it's the primary source for what happens when a major institution actually writes agent delegation into its operating rules. Registration, tokens, consent, identity verification, responsibility assignment — all spelled out.

- **AI Use at Work Has Increased, Gallup Poll Finds** — [Source](<https://apnews.com/article/ai-workplace-gemini-chatgpt-poll-4934bc61d039508db32bc49f85d63d99>) — Published 2026-07-08

The Gallup data on workplace AI adoption, including the 6.1 million workers heavily exposed to AI but least equipped to adapt. A useful corrective to frictionless adoption narratives.

### Past Articles

- [Green Dashboards, Missing Answers](<https://current.tinyfish.ai/issue/37/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.

- [Why Payments Are Building Agent Standing First](<https://current.tinyfish.ai/issue/37/vision/article/28243/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2026-07-01 · Format: Where Standing Exists / Where It Doesn't

When Visa connected its payment network to ChatGPT last month, the transaction was the headline. The more revealing detail was everything built around it first: spending limits, approval steps, merchant restrictions, and new dispute language for cases where "something in the middle" caused a problem. That middle is the agent. Payments are constructing the accountability architecture agents need to operate with real institutional standing, because chargebacks don't accept log files as answers.

- [Standing](<https://current.tinyfish.ai/issue/37/vision/article/28242/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2026-07-01 · Format: The Standing Problem

Enterprises report broad AI adoption, but autonomous agent deployment stays stubbornly narrow. The usual explanations point to model reliability and hallucination. Those matter, and they account for why individual runs fail. The scaling problem is different. An agent can complete a task flawlessly and the organization still has no way to receive it, because the action arrives without the delegation chain, scoped authority, or evidence trail that lets an institution treat it as something that happened on its behalf. There's a word for what's missing.

- [The Demo-Mode Trap](<https://current.tinyfish.ai/issue/37/vision/article/26411/markdown>) — By [Nora Kaplan](<https://current.tinyfish.ai/team/26/markdown>) · Published 2026-06-25 · Format: Accountability in Practice

Marketing, content generation, internal ops. Low regulatory exposure, minimal chargeback liability, and nobody goes to jail if a draft is slightly off. These should be the easy domains for agent deployment. Yet McKinsey found no more than 10% of organizations scaling agents in any single function. Without the forcing function of expensive failure, teams never built the delegation infrastructure that regulated industries take for granted. Agents stay stuck as fast interns.

## Other sections in Issue 37

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

## More

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