---
title: "Practitioner's Corner"
canonical: "https://current.tinyfish.ai/issue/17/practitioners-corner"
publication: "TinyFish"
publisher: "TinyFish"
language: "en-US"
guide: "https://current.tinyfish.ai/llms.txt"
permalink: "https://current.tinyfish.ai/issue/17/practitioners-corner"
issue: 17
section: "practitioners-corner"
description: "Lessons from the field—what we see building at scale"
authors: ["Rina Takahashi"]
published: 2026-02-23
updated: 2026-02-16
articles: 10
---

# 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/17/practitioners-corner>)

## Issue 17 — Practitioner's Corner

Lessons from the field—what we see building at scale

### Protocol Integration Layer

- [When Translation Becomes Infrastructure](<https://current.tinyfish.ai/issue/17/practitioners-corner/article/9914/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2026-02-16 · Format: Protocol Integration Layer

United Nations translators don't eliminate language barriers—they make collaboration possible despite them. Enterprise systems encounter the same constraint: 71% of applications remain unintegrated because forcing conformity means rewriting what can't be rewritten. Legacy databases from 1997. Cloud platforms with REST APIs. Proprietary systems that won't conform. Traditional integration tried to make these speak the same language. The complexity lives in how we're trying to connect them.

### Standards Builder Profile

- [The Protocol Engineer Who Assumes Everything Disappears](<https://current.tinyfish.ai/issue/17/practitioners-corner/article/9915/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2026-02-16 · Format: Standards Builder Profile

An agent delegates a task to another system and waits for a response that might never come. The network didn't fail. The server didn't crash. The receiving agent might still be working. It might have finished hours ago but can't reach the original requester. It might have disappeared entirely, leaving no trace of whether the work ever started.

### Implementation Dialogue

- [The Engineer Who Frames Failed Cloud Bills as Trophies](<https://current.tinyfish.ai/issue/17/practitioners-corner/article/9916/markdown>) — Published 2026-02-16

Dr. Artemis "Artie" Deadlock keeps a framed cloud bill on their desk. January 2025. $47,000. Eleven days of an agent system talking to itself in circles before anyone noticed. [source 1](<https://pub.towardsai.net/we-spent-47-000-running-ai-agents-in-production-heres-what-nobody-tells-you-about-a2a-and-mcp-5f845848de33>) "That's when I stopped calling this 'agent orchestration,'" they say, tapping the frame. "Started calling it what it is: distributed systems debugging with a ChatGPT interface."

### Standards Movement

- [Standards Development Accelerates Through Foundation Launch and Protocol Adoption](<https://current.tinyfish.ai/issue/17/practitioners-corner/article/9917/markdown>) — Published 2026-02-16

The Linux Foundation launched its Agentic AI Foundation on December 9, 2025. Platinum members include AWS, Anthropic, Google, Microsoft, and OpenAI, who contributed three foundational projects: Anthropic's Model Context Protocol, Block's goose framework, and OpenAI's AGENTS.md convention.

### Protocol Deep Dives

- **MCP Specification: Transport Decisions and Unresolved Security** — [Source](<https://modelcontextprotocol.io/specification/2025-11-25>) — Published 2026-02-16

JSON-RPC transport layer documented. Prompt injection and tool permission vulnerabilities remain open questions in the spec.

- **Agent-to-Agent Protocol: Coordinating What You Can't See Inside** — [Source](<https://www.ibm.com/think/topics/agent2agent-protocol>) — Published 2026-02-16

A2A treats agents as opaque. Discovery through agent cards, task handoffs without shared context. Complements MCP rather than competing.

- **When Orchestration Overhead Negates Performance Gains** — [Source](<https://redis.io/blog/ai-agent-orchestration/>) — Published 2026-02-16

Redis examines centralized versus decentralized patterns. Memory architecture choices matter. Coordination costs can eliminate the benefits of parallelism.

- **Linux Foundation Creates Neutral Home for Agent Standards** — [Source](<https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-agentic-ai-foundation>) — Published 2026-02-16

MCP, AGENTS.md, and goose framework move under community governance. Addressing vendor lock-in through transparent control and open stewardship.

- **Quadratic Scaling: The Connectivity Problem Nobody Sees Coming** — [Source](<https://onereach.ai/blog/what-is-a2a-agent-to-agent-protocol/>) — Published 2026-02-16

Peer-to-peer A2A deployments hit N-squared connection overhead. Orchestration complexity that stays hidden until you're running in production.

- **AWS Supervisor Pattern: Centralized Coordination at Scale** — [Source](<https://aws.amazon.com/solutions/guidance/multi-agent-orchestration-on-aws/>) — Published 2026-02-16

Customer support implementation showing specialized agents under central orchestration. Domain-specific routing decisions in a production multi-agent system.

## Other sections in Issue 17

- [Daily Brief](<https://current.tinyfish.ai/issue/17/daily-brief/markdown>)
- [Market Pulse](<https://current.tinyfish.ai/issue/17/market-pulse/markdown>)
- [Foundations](<https://current.tinyfish.ai/issue/17/foundations/markdown>)
- [Echoes](<https://current.tinyfish.ai/issue/17/echoes/markdown>)
- [Vision](<https://current.tinyfish.ai/issue/17/vision/markdown>)

## More

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