--- title: "Foundations" canonical: "https://current.tinyfish.ai/issue/15/foundations" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/15/foundations" issue: 15 section: "foundations" description: "Conceptual clarity earned from building at scale" authors: ["Rina Takahashi"] published: 2026-02-08 updated: 2026-02-04 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 15 — Foundations Conceptual clarity earned from building at scale ### What Building Teaches Builders - [What You're Measuring and How You're Measuring It]() — By [Rina Takahashi]() · Published 2026-02-03 · Format: Field Guide Your agent passes testing, fails in production. Another completes tasks while taking paths you can't see are fragile. A third does exactly what it should but scores zero on task completion. The evaluation says "working"—but working how? Teams get confusing results not because agents are unpredictable, but because what they're measuring and how they're measuring it answer different questions entirely. ### Tools & Techniques - [When Restarting From Scratch Costs Less Than Saving Progress]() — By [Rina Takahashi]() · Published 2026-02-03 · Format: Tools in Context The alert fires at 2am. Workflow crashed at step four of seven. Should those three successful steps have been saved somewhere? For teams running thousands of high-frequency workflows daily, the answer surprises: restart from scratch. The coordination overhead—state management across workers, cleanup routines, synchronization delays—costs more than re-executing from the beginning. At certain scales and workflow durations, accepting occasional failures beats implementing elaborate persistence. Production math reveals when operational simplicity wins. - [What It Actually Takes to Resume a Crashed Workflow]() — By [Rina Takahashi]() · Published 2026-02-03 · Format: Tools in Context A compliance workflow authenticates, scrapes forty pages of transaction history, then waits three hours for manual legal review before continuing. You can't keep a browser running that long. Sessions expire, memory leaks accumulate, containers get recycled on schedule. The workflow must terminate and resume hours later with state intact. For teams running long workflows across distributed fleets, checkpoints stop being optional. But state persistence brings specific overhead: synchronization delays, cleanup routines, session tracking across workers. Here's what coordination actually requires. ### Pattern Recognition - [Identity Vendors Rush Agent IAM Products in January]() — Published 2026-02-04 Four identity vendors shipped agent-specific IAM within three weeks. Microsoft's Entra Agent ID launched January 20. Cloud Security Alliance released MAESTRO framework January 15. Qualys shipped Agent Grant January 6. Exabeam rolled out Agent Behavior Analytics earlier that month. ### Questions Worth Asking Before you deploy anything to production, you need better questions than "does it work?" Most systems fail in the gap between functional and production-ready. Not from broken code. From teams that never asked what happens when things break, who pays for it, or who fixes it at 3 AM. These questions come from operating systems under real load. Each one surfaces a factor that gets overlooked in demos but becomes expensive after launch. The right question at the right time can save you from mistakes that only become obvious when you're already live. - **What Happens When This Breaks?** — [Source]() — Published 2026-02-04 Tag: Contractual Consequences If you miss targets, does someone write a check or just send an apologetic email? Real SLAs trigger rebates and contract penalties. Everything else is an SLO you're tracking internally. That difference determines whether you architect for guarantees or aspirations. - **Can You Explain Next Month's Bill?** — [Source]() — Published 2026-02-04 Tag: Cost Visibility When cloud costs spiral, can you trace spending to specific workloads? Production systems need cost monitoring that spots optimization opportunities before budget meetings turn awkward. Guessing at invoices means you're not ready to scale. Period. - **Who Fixes This at 3 AM?** — [Source]() — Published 2026-02-04 Tag: Recovery Planning Incident response plans define who does what when systems fail. Without clear ownership and coordination tools, disruptions become disasters. The gap between a hiccup and a crisis? Knowing exactly who responds, how they coordinate, what recovery actually looks like. - **Is Your Infrastructure Clicking or Coded?** — [Source]() — Published 2026-02-04 Tag: Infrastructure Codification Provisioning through cloud consoles puts you at the lowest maturity level. Elite teams manage production infrastructure through version-controlled IaC with automated validation. Manual provisioning creates drift you can't track. It doesn't scale. - **Can You See What's Actually Happening?** — [Source]() — Published 2026-02-04 Tag: Observability Implementation For AI agents, 89% have observability while only 52% have evaluation frameworks. That gap matters. You need visibility into behavior before you can measure quality. Observability shows you what your system does under real conditions, not what you hoped it would do. - **After Incidents, Do You Hunt Blame?** — [Source]() — Published 2026-02-04 Tag: Cultural Indicators The most sophisticated toolchain fails if teams operate in silos. Elite organizations conduct blameless post-mortems focused on systemic root causes, not guilty individuals. Culture determines whether your technical capabilities translate to actual performance. Tools alone never do. ### In Dialogue With Complexity - [An Interview with Non-Deterministic Output About Refusing to Be the Same Twice]() — Published 2026-02-04 We meet Nondee in what they describe as "the space between executions," a liminal zone where LLM outputs exist before being captured by checkpoint systems. They're fidgeting, constantly shifting form, never quite the same twice. When I ask them to sit still for the interview, they laugh. "That's the whole problem, isn't it?" ## Other sections in Issue 15 - [Daily Brief]() - [Market Pulse]() - [Practitioner's Corner]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()