--- title: "Foundations" canonical: "https://current.tinyfish.ai/issue/4/foundations" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/4/foundations" issue: 4 section: "foundations" description: "Conceptual clarity earned from building at scale" authors: ["Rina Takahashi"] published: 2025-11-20 updated: 2025-11-20 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 4 — Foundations Conceptual clarity earned from building at scale ### What Building Teaches Builders - [What Reliability Actually Means in Adversarial Environments]() — By [Rina Takahashi]() · Published 2025-11-20 · Format: Field Guide We've seen web agent systems maintain 100% availability while delivering zero correct results. Every request completes successfully. Every HTTP response returns 200. The infrastructure is "up." But every extraction triggers detection and returns error pages instead of data. Traditional uptime metrics can't capture what's actually broken. When the web actively resists automation, reliability means something different than availability percentages—something most teams don't measure until after deployment. ### Web Evolution's Lessons - [The Paradox of Web Transparency]() — By [Rina Takahashi]() · Published 2025-11-20 · Format: Web Archaeology View Source still works on every website. The HTML arrives readable, transparent, exactly as Tim Berners-Lee designed it in 1991. The web's founding principle of radical openness never disappeared. The architecture still assumes anyone can see how things work. ### Pattern Recognition from the Field - [Pilots Succeed, Production Fails: The Agent Deployment Gap]() — Published 2025-11-20 I keep seeing the same thing: companies run successful AI agent pilots, then production deployment stalls. Pilots jumped from 37% to 65% in one quarter. Production deployment? Still stuck at 11%. MIT found only 5% of custom enterprise AI tools actually make it to production. ### Questions Worth Asking Most evaluation criteria focus on what works in controlled conditions. Feature completeness. Benchmark performance. API elegance. Then production happens. The expensive mistakes come from asking the wrong questions early. Teams evaluate capabilities instead of operational burden. They test performance with clean data instead of the messy reality their systems will face. They assume debuggability instead of verifying it. After enough deployments, you learn which questions actually predict success. They're not the ones in vendor comparison matrices. They're the ones that reveal what happens when demos meet real traffic, when requirements change, when something breaks at 3am and you need answers fast. - **What Changes Between Demo and Your Data?** — [Source]() — Published 2025-11-20 Tag: Demo Reality Demos run on sanitized datasets with known edge cases handled. Your production data has nulls in unexpected places, encodings that break parsers, and user behavior no QA team anticipated. Ask for deployment timelines on real customer data, not feature completeness on their test set. - **Can You Ask New Questions When It Breaks?** — [Source]() — Published 2025-11-20 Tag: Debugging Access Monitoring shows you that something failed. Observability lets you figure out why without redeploying instrumentation. When production breaks at 3am, you need to interrogate the system with questions you didn't think to ask yesterday. Predefined dashboards won't cut it. - **Does This Work With What You Already Run?** — [Source]() — Published 2025-11-20 Tag: Stack Integration Your best deployment platform is the one your ops team already knows. If this requires new infrastructure or doesn't integrate with existing monitoring, you're not evaluating a tool. You're committing to a migration project that'll consume six months nobody planned for. - **Who Owns Changes After Initial Deployment?** — [Source]() — Published 2025-11-20 Tag: Change Velocity Requirements shift constantly. New data sources, modified workflows, unexpected use cases. Can your team adapt the system themselves, or does every adjustment require vendor involvement? This determines whether your investment compounds or becomes technical debt you're stuck maintaining. - **Where Does Performance Degrade Under Real Traffic?** — [Source]() — Published 2025-11-20 Tag: Load Behavior Test conditions reveal nothing about production behavior. What happens at 10x your demo load during a traffic spike? Does latency climb linearly or does something cliff-dive? The architectural choices that seem theoretical now determine whether you're rebuilding when actual users arrive. - **What's the Daily Maintenance Burden?** — [Source]() — Published 2025-11-20 Tag: Operational Tax Some infrastructure fades into the background. Other systems demand constant attention. Before committing, understand monitoring requirements, rollback procedures, incident patterns. Production readiness reviews take months at scale because this question has expensive answers vendors won't surface in sales calls. ### In Dialogue With Complexity - [In Conversation with the Reject All Button]() — Published 2025-11-20 *We're conducting a series of conversations with the unsung heroes of the modern web—the UX patterns that accidentally became critical infrastructure for AI agents. Today's subject may be the most-clicked, least-wanted button on the internet. This conversation is, of course, hypothetical. The Reject All Button cannot actually speak. But if it could...* ## Other sections in Issue 4 - [Daily Brief]() - [Market Pulse]() - [Practitioner's Corner]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()