--- title: "Foundations" canonical: "https://current.tinyfish.ai/issue/9/foundations" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/9/foundations" issue: 9 section: "foundations" description: "Conceptual clarity earned from building at scale" authors: ["Nora Kaplan","Rina Takahashi"] published: 2025-12-29 updated: 2025-12-25 articles: 11 --- # 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 9 — Foundations Conceptual clarity earned from building at scale ### What Building Teaches Builders - [The Observation Gap in Agent Delegation]() — By [Nora Kaplan]() · Published 2025-12-24 · Format: Field Guide Your competitor pricing agent just navigated authentication flows across two thousand retail sites, handled bot detection that varies by region, interpreted A/B tested structures, and distinguished genuine price changes from temporary glitches. It made hundreds of judgment calls about when to retry, when to escalate, whether anomalies matter. ### Tools & Techniques - [What High-Frequency Monitoring Actually Catches]() — By [Rina Takahashi]() · Published 2025-12-24 · Format: Tools in Context Check a website once and you learn whether it's working. Check it every minute for weeks and you learn how it behaves. High-frequency monitoring trades depth for speed—tests stay simple because they need to complete fast. But that speed reveals something synthetic checks can't: the patterns that emerge when you're watching constantly. Bot detection rolling out overnight. Site structures shifting during inventory updates. The things that break in production, as they're breaking. - [When Shadow Testing Reveals What Monitoring Misses]() — By [Rina Takahashi]() · Published 2025-12-24 · Format: Tools in Context Shadow testing runs your new code against real production traffic for days or weeks, processing every edge case your infrastructure encounters while users see results from your current system. It's expensive—you're running everything twice. But some things about web agent reliability only become visible when you're handling actual authentication challenges, actual regional variations, actual bot detection patterns. The complexity that monitoring catches quickly, shadow testing catches thoroughly. ### Pattern Recognition - [Companies Keep Buying GPUs They Can't Use]() — Published 2025-12-24 Enterprises plan massive GPU expansion in 2025. Ninety-six percent will add capacity. Yet only 7% achieve above 85% utilization during peak periods. Fifteen percent report fewer than half their GPUs are actually working, even when demand is highest. ### Questions Worth Asking Watch any evaluation process and you'll see the same mistake. Teams compare tools before they know what they're comparing them against. We've watched dozens of production deployments. The pattern holds: successful teams define evaluation criteria first. They know their data infrastructure. They understand integration requirements. They've calculated what a decision costs, not just what the subscription costs. These questions predict what works at scale. They come from watching things break and watching things hold. Use them before the demo starts and the pitch begins. - **What Does Good Enough Look Like?** — [Source]() — Published 2025-12-24 Tag: Success Metrics Define measurable success criteria before you evaluate anything. Translate business requirements into thresholds you can test against. The right accuracy number matters less than knowing which threshold serves your use case. Build the scorecard first. - **Is Your Data Ready for This?** — [Source]() — Published 2025-12-24 Tag: Data Infrastructure Your data infrastructure predicts adoption more than model sophistication does. Quality, accessibility, governance. Without clean, relevant data in the right place, sophisticated models just fail faster. Evaluate data readiness before evaluating tools. - **What's the Real Cost Per Decision?** — [Source]() — Published 2025-12-24 Tag: Resource Efficiency Pricing pages lie by omission. They show monthly fees, not computational costs per action. Calculate cost per decision: compute, maintenance, failure handling. Agents deployed without rigorous evaluation burn resources while delivering inconsistent results. - **Does This Embed or Just Connect?** — [Source]() — Published 2025-12-24 Tag: Integration Requirements API integrations create maintenance overhead and data sync problems. Look for tools that embed directly into core systems: CRM, marketing automation, customer service. Real-time access to unified data generates accurate outputs. Manual transfers introduce security risks and staleness. - **Does Multi-Agent Architecture Solve Anything?** — [Source]() — Published 2025-12-24 Tag: Architectural Complexity One agent with sufficient tools often beats three agents coordinating. Decision-making and flow-control overhead can exceed multi-agent benefits. Splitting tasks across agents distributes problems without necessarily improving outcomes. Confirm the complexity adds value. - **Can You Explain This to Leadership?** — [Source]() — Published 2025-12-24 Tag: Transparency Requirements Autonomy demands transparency. Systems should log every reasoning step, making consequences explicit before execution. If you can't explain why the agent made that choice to your CFO, you can't trust it with decisions that matter. ### In Dialogue With Complexity - [An Interview with The Forty-Dollar Threshold]() — Published 2025-12-24 We're sitting in a conference room where someone has just presented a business case for automation. The numbers are stark: $127 per manual ticket resolution versus $43 with an AI agent. The decision feels inevitable, almost mechanical. But there's a moment—right when the CFO nods—where something fundamental shifts in how the company thinks about work itself. ## Other sections in Issue 9 - [Daily Brief]() - [Market Pulse]() - [Practitioner's Corner]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()