--- title: "Vision" canonical: "https://current.tinyfish.ai/issue/36/vision" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/36/vision" issue: 36 section: "vision" description: "Where human-AI collaboration is heading" authors: ["Rina Takahashi","Nora Kaplan"] published: 2026-07-06 updated: 2026-07-02 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 36 — Vision Where human-AI collaboration is heading ### The Standing Problem - [Standing]() — By [Rina Takahashi]() · 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. ### Where Standing Exists / Where It Doesn't - [Why Payments Are Building Agent Standing First]() — By [Rina Takahashi]() · 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. - [Green Dashboards, Missing Answers]() — By [Rina Takahashi]() · 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. ### Defining Agent-Authorized - [The Agent Didn't Create the Authorization Problem. A Hypothetical Compliance Officer Explains What It Did.]() — Published 2026-07-01 Five weeks before the EU AI Act's high-risk compliance deadline hits on August 2, 2026, a particular kind of headache has settled into the compliance departments of financial institutions across Europe and beyond. The headache has a name. Or rather, it doesn't, which is the problem. What does "agent-authorized" mean inside a control framework built entirely for humans? ### Autonomy Belongs to the System - [Autonomy Lives in the Workflow, Not the Model]() — By [Nora Kaplan]() · Published 2026-07-01 On TheAgentCompany's workplace benchmark, the best models [score 70.8%](https://www.emergentmind.com/topics/theagentcompany-benchmark) on a bounded task like requesting time off but drop to 35.3% on complex customer routing. Same models, same environment. What changed is the work surrounding them. ### Further Reading - **Visa Plugs Its Payment Network Into ChatGPT, Letting AI Agents Shop and Pay for Users** — [Source]() — Published 2026-07-01 The most revealing detail here isn't that Visa connected to ChatGPT. It's the scaffolding they had to build around it: spending caps, merchant restrictions, multi-step approvals, dispute flows. Read this as a blueprint for what delegated authority actually looks like when real money is on the line. - **The State of AI in 2025: Global Survey** — [Source]() — Published 2026-07-01 McKinsey's survey captures a striking gap: 88% of organizations report using AI in at least one function, yet no single function has scaled agents past 10%. That number tells you exactly where the industry sits, somewhere between enthusiasm and operational reality. - **The 2026 AI Index Report** — [Source]() — Published 2026-07-01 Stanford HAI documents a tension worth sitting with: agent benchmark performance is climbing fast, AI incidents reached 362, and responsible-AI reporting remains patchy at best. The juxtaposition of rising capability and lagging accountability is the story of this moment in the field. - **MCP Authorization Specification (2025-06-18)** — [Source]() — Published 2026-07-01 Protocol specs rarely make for compelling reading, but this one matters. It turns "delegated access" from a hand-wavy concept into concrete engineering: OAuth resource indicators, audience validation, explicit prohibitions on token passthrough. If you want to understand how agent permissions get scoped in practice, start here. - **EU AI Act: Regulatory Framework** — [Source]() — Published 2026-07-01 The EU AI Act's enforcement milestones are now arriving on dated schedules, turning human oversight and activity logging from aspirational best practices into legal requirements. Worth tracking because governance obligations have a way of becoming system requirements faster than engineering teams expect. - **LLM01:2025 Prompt Injection** — [Source]() — Published 2026-07-01 OWASP's top-ranked LLM risk lays out why indirect prompt injection gets worse, not better, as agents gain more authority and access to more systems. The mitigations they outline are architectural rather than cosmetic, which tells you something about the depth of the problem. ### Past Articles - [The Demo-Mode Trap]() — By [Nora Kaplan]() · 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. - [Why the Most Regulated Industries Are Deploying Agents First]() — By [Nora Kaplan]() · Published 2026-06-25 · Format: Accountability in Practice Mastercard's Agent Pay announcement read more like a policy document than a product launch. That's the point. Payments, financial compliance, and regulated operations are deploying agents faster than anyone expected, drawing on decades of managing authorization, audit trails, and dispute resolution to provide exactly the scaffolding agents need. Regulation pre-answered the hardest delegation questions. Everyone else is still improvising. - [The Accountability Inversion]() — By [Nora Kaplan]() · Published 2026-06-25 · Format: Central Thesis The assumption is straightforward: better models unlock broader autonomy, and the most technically adventurous organizations lead agent adoption. The evidence points somewhere unexpected. Heavily regulated, accountability-dense environments are reaching production first. Compliance monitoring, clinical documentation, financial back-office. The places you'd expect to move slowest are moving fastest. The gating factor for agent deployment at scale turns out to be whether anyone can later prove who authorized what, within what limits, and where the records live. Banks solved a version of this problem fifty years ago. The structural logic is worth revisiting. - [The Conditions for Meaning]() — By [Nora Kaplan]() · Published 2026-06-18 · Format: Individual Shift / Organizational Conditions If the individual question is whether curating AI outputs builds real expertise, the organizational question is whether anyone is designing work so the answer matters. Research identifies specific choices — autonomy, surveillance posture, explainability — that determine whether augmented work retains meaning or hollows out. Eighty-four percent of organizations haven't redesigned jobs around AI. They're making these decisions by accident, and the consequences compound in ways no productivity metric will catch. ## Other sections in Issue 36 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Echoes]() ## More - [Publication guide]() - [Issue archive]()