--- title: "Foundations" canonical: "https://current.tinyfish.ai/issue/8/foundations" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/8/foundations" issue: 8 section: "foundations" description: "Conceptual clarity earned from building at scale" authors: ["Rina Takahashi","Nora Kaplan"] published: 2025-12-22 updated: 2025-12-18 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 8 — Foundations Conceptual clarity earned from building at scale ### What Building Teaches Builders - [Reading What Your System Already Knows About Inflection Points]() — By [Rina Takahashi]() · Published 2025-12-17 · Format: Field Guide Your infrastructure knows it's outgrown itself before you do. The signals are there—not in dashboards or performance metrics, but in patterns most teams mistake for problems to solve. Engineers building the same abstraction for the third time. Error messages that stopped describing failures and started describing struggle. Costs that scale with complexity instead of volume. Each looks fixable. Together, they mark something else entirely. Most teams spend months fighting symptoms before they recognize what their system has been trying to tell them all along. ### Tools & Techniques - [When Agents Need Permission]() — By [Nora Kaplan]() · Published 2025-12-17 · Format: Tools in Context The first time your team deploys an agent that does something consequential—updating prices, flagging fraud, triggering workflows—someone asks: "But what if it's wrong?" That question lands differently when these aren't read-only operations. So teams reach for approval tools. The agent proposes an action. A human reviews it. Then, and only then, does anything happen. This isn't distrust. It's how organizations learn what their agents can actually handle. - [When Agents Ask for Advice Instead of Permission]() — By [Nora Kaplan]() · Published 2025-12-17 · Format: Tools in Context You're watching another Slack notification. The agent wants approval for a pricing update based on competitor movement. You glance at the proposal, already knowing you'll approve it—you've approved fifty identical decisions this week. The bottleneck isn't the technology anymore. It's you. This is when teams shift to advisory tools: agents operate autonomously but flag strategic decisions that need human wisdom. The work changes from gatekeeping to guidance. ### Pattern Recognition - [Vendors Ship Evaluation Tools Alongside Their Agents]() — Published 2025-12-17 Something odd happened in December. AWS announced 13 pre-built evaluation systems for agents. Salesforce launched a Testing Center. Multiple vendors released evaluation frameworks within weeks of their agent products. ### Questions Worth Asking Most evaluation questions focus on capabilities. What can the AI do in theory? But that's not what predicts success at scale. What matters is operational reality. How systems behave under production conditions. What they demand from your organization. Where they break and how you recover. These questions cut through demo magic to what actually determines whether AI delivers value or becomes another abandoned pilot. We ask them not because we're skeptical, but because we've seen what happens when you wait too long to ask them. - **What Breaks Between Demo and Production?** — [Source]() — Published 2025-12-17 Tag: Integration Reality Demos run in controlled environments. Production means authentication layers, compliance workflows, legacy systems that don't speak to each other. The gap between these worlds kills more pilots than bad models. Can they walk you through the actual integration path? - **Does This Fade or Demand Attention?** — [Source]() — Published 2025-12-17 Tag: Operational Burden Good infrastructure disappears. You deploy it, it runs, you move on. Bad AI demands constant tuning, manual corrections, checking outputs. If your team spends more time managing the system than using it, you're not creating value. How much attention do production deployments actually need? - **Can You Catch Failures Before They're Expensive?** — [Source]() — Published 2025-12-17 Tag: Evaluation Honesty Most teams gather evaluation metrics without translating them into improvements. The metrics graveyard problem. What you need: a framework that predicts production performance, not one that generates reassuring dashboards. Does their evaluation actually prevent costly failures or just document them? - **What's Right When Decisions Are Subjective?** — [Source]() — Published 2025-12-17 Tag: Ground Truth Traditional ML compares outputs against correct answers. But subjective decisions have no single right answer. That's exactly where AI promises value and where defining correctness gets messy. How does the system measure quality when ground truth is fuzzy or contested? - **Where Does Automation Actually Help?** — [Source]() — Published 2025-12-17 Tag: Human Handoff Full automation sounds appealing. Augmenting humans works better. The hard part is designing handoffs where agents handle routine work but escalate judgment calls without creating friction. Does the hybrid workflow save effort or just redistribute it? - **Who Owns Outcomes When Things Break?** — [Source]() — Published 2025-12-17 Tag: Ownership Clarity Most failed AI projects have vague ownership. IT builds, data science models, business waits. Nobody manages rollout, maintains the system, or tracks ROI. Without a process owner accountable for outcomes, you get abandoned pilots. Who's actually responsible here? ### In Dialogue With Complexity - [An Interview with the Format That Became a Protocol]() — Published 2025-12-17 We're sitting in what Jay Son describes as "a very well-structured space." Given that he's literally a data serialization format, this makes sense. He's been the backbone of web communication since 2001, quietly passing messages between systems. Now he finds himself at the center of something bigger: the agent-tool standardization moment. ## Other sections in Issue 8 - [Daily Brief]() - [Market Pulse]() - [Practitioner's Corner]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()