--- title: "Foundations" canonical: "https://current.tinyfish.ai/issue/5/foundations" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/5/foundations" issue: 5 section: "foundations" description: "Conceptual clarity earned from building at scale" authors: ["Nora Kaplan","Rina Takahashi"] published: 2025-12-01 updated: 2025-11-27 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]() ## Issue 5 — Foundations Conceptual clarity earned from building at scale ### What Building Teaches Builders - [When Extraction Succeeds But Data Goes Wrong]() — By [Nora Kaplan]() · Published 2025-11-27 · Format: Field Guide Your web agent extracts data successfully. Pipelines flow, dashboards update, everything looks operational. Then someone notices the competitor prices don't match what's actually on the website. Inventory counts show gaps that shouldn't exist. A business decision gets made on data that was technically extracted but fundamentally incorrect. ### Web Evolution's Lessons - [The Shopping Cart That Made State Management Adversarial]() — By [Rina Takahashi]() · Published 2025-11-27 · Format: Web Archaeology In June 1994, Lou Montulli needed to solve HTTP's statelessness—how do you remember a shopping cart when every page load forgets the last? His Netscape team rejected simpler solutions because they'd enable cross-site tracking. So they designed cookies with privacy protections: information would only flow between users and the specific sites they visited. The architecture had a gap. ### Pattern Recognition from the Field - [The Agent Deployment Gap Everyone's Ignoring]() — Published 2025-11-27 Here's what I keep seeing: vendors announce dozens of agents while actual deployments stall out. Microsoft Ignite paraded Agent 365 and specialized agents. Google updated Vertex AI Agent Builder. OpenAI shipped agent-optimized models. Meanwhile, 65% of enterprises are stuck running pilots. Only 11% reach production. ### Questions Worth Asking The questions you ask before choosing a tool reveal how much production experience you have. Feature matrices and vendor demos tell you what works in controlled environments. They don't tell you what breaks at 3am or what costs you didn't see coming. These questions come from operating systems at scale and watching what actually matters versus what just sounds good in architecture reviews. They're not in the comparison spreadsheets. They predict whether you'll still be happy with this choice six months into production, when the real costs become visible and the complexity tax comes due. - **Can You Actually Promise Uptime?** — [Source]() — Published 2025-11-27 Tag: Reliability Guarantees Legal writes 99.9% availability into contracts before engineering confirms it's achievable. Your architecture either supports deterministic SLAs or it doesn't. Probabilistic systems can't make hard promises. Check technical feasibility before the contract goes out. - **What's the Real Cost After Launch?** — [Source]() — Published 2025-11-27 Tag: Total Ownership Google estimates 40-90% of total cost of ownership comes after production launch. That architecture with the attractive licensing price? Calculate what percentage of your budget will go to keeping it running versus building new features. Launch price isn't real price. - **Does This Enforce Consistency or Require It?** — [Source]() — Published 2025-11-27 Tag: Standards Enforcement Sixty-six percent of engineering leaders cite inconsistent standards as their biggest production readiness blocker. Your tool either enforces best practices automatically or demands constant human vigilance. Manual checks get skipped under pressure. Every time. - **Will Complexity Outpace Your Team's Growth?** — [Source]() — Published 2025-11-27 Tag: Complexity Tax System complexity compounds faster than headcount. Engineering expertise splinters across multiple systems. Learning curves steepen. More time goes to maintenance than building value. Look hard at whether this architecture's complexity actually serves business needs or just sounds impressive in reviews. - **What's Your Error Budget and MTTR?** — [Source]() — Published 2025-11-27 Tag: Error Recovery A 99.99% SLO over thirty days gives you roughly four minutes of allowable downtime. When monitoring, ownership, and runbooks exist before launch, mean time to recovery drops significantly. Does this system help you stay within budget and recover fast when you breach it? - **Does This Vendor Have Critical Mass?** — [Source]() — Published 2025-11-27 Tag: Vendor Viability Architecture evaluation should assess whether the component and its vendor have critical mass in their marketplaces. Technically excellent tools from vendors without staying power create infrastructure risk. You're betting on their survival. Know what you're betting on. ### In Dialogue With Complexity - [An Interview With v2.0, The API Version Nobody Wanted to Migrate To]() — Published 2025-11-27 We found v2.0 in a dimly lit corner of a production environment, surrounded by monitoring dashboards showing embarrassingly low adoption metrics. Despite being released eighteen months ago, v2.0 handles less than 12% of the traffic while v1 continues serving the vast majority of requests. There's a weariness here, the exhaustion of being technically superior but operationally irrelevant. ## Other sections in Issue 5 - [Daily Brief]() - [Market Pulse]() - [Practitioner's Corner]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()