---
title: "Issue 10"
canonical: "https://current.tinyfish.ai/issue/10"
publication: "TinyFish"
publisher: "TinyFish"
language: "en-US"
guide: "https://current.tinyfish.ai/llms.txt"
permalink: "https://current.tinyfish.ai/issue/10"
issue: 10
description: "The vocabulary you use to describe your systems is quietly lying to you. This week: how yesterday's solutions became today's invisible architecture traps, and why your monitoring might be creating the chaos it promises to prevent."
authors: ["Sable Whitford","Nora Kaplan","Rina Takahashi"]
published: 2026-01-05
updated: 2026-11-05
articles: 94
---

# 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](<https://current.tinyfish.ai/issue/10>)

## Issue 10

The vocabulary you use to describe your systems is quietly lying to you. This week: how yesterday's solutions became today's invisible architecture traps, and why your monitoring might be creating the chaos it promises to prevent.

### [Daily Brief](<https://current.tinyfish.ai/issue/10/daily-brief/markdown>)

Your daily digest of web developments through the lens of enterprise agent deployment

- [Google Lets Schools Keep Search Without Gemini. The AI Overviews Come Along Anyway.](<https://current.tinyfish.ai/issue/10/daily-brief/article/60988/markdown>) — By [Sable Whitford](<https://current.tinyfish.ai/team/201/markdown>) · Published 2026-11-04

On Tuesday, which was also Election Day, Google announced a K-12 policy that switches Gemini, Gemini Notebook and **Search off by default** for schools using its education software. A Google education VP told the New York Times that "Search and AI are deeply integrated," so districts that ban AI would lose Search as well. Bernie Sanders called it **"extortion,"** and Sen. Richard Blumenthal and NYC Mayor Zohran Mamdani joined in. Within hours Google **partly walked it back**: schools can now turn on Search by itself, without Gemini. That Search still puts AI Overviews on the results page, though, so **the fight now is over what "AI off" means.**

- **Proxy Traffic Leaving the White House Network?** — [Source](<https://layer3intel.com/blog/residential-proxies-white-house-network>) — Published 2026-11-04

Layer3 Intel says residential proxy traffic exited AS2650, the Executive Office of the President's network, 236 times in 30 days through 28 proxy services. It says it wasn't even looking. Its guess is that someone working late has a device carrying a proxy SDK. Treat that as a theory: no device has been named, and six public IPs can sit in front of a lot of machines.

- **DreamHost Had Uninvited Guests Since August** — [Source](<https://techcrunch.com/2026/11/04/hackers-stole-dreamhost-customer-files-and-inboxes-during-months-long-attack>) — Published 2026-11-04

DreamHost confirmed that attackers used a file manager bug to steal session tokens, customer emails and files, and that they got in back in August. That's a long stay at a host with about 400,000 paying customers. DreamHost says it's unrelated to PHP2Shell. If you're a customer, rotating credentials today is a sensible move.

- **PHP2Shell's Hangover Gets a Sequel** — [Source](<https://kaspersky.com/blog/php2shell-two-weeks-after-patches/56647>) — Published 2026-11-04

PHP2Shell was a pair of 9.2-severity bugs that put NASA, Wikipedia and the White House at risk. Two weeks after the patches, Kaspersky counts nearly 30 million servers still unpatched, plus a third, still-open flaw (CVE-2026-115560). Working exploits keep multiplying, though there's no confirmed mass-breach wave yet. Tolmo's Matt Suiche says AI bug hunting is exposing 40 years of legacy code, and that's today's big argument. AI can find a bug in minutes. Someone still has to book maintenance windows for 30 million servers.

- **Can DNS Tell You It's a Bot?** — [Source](<https://idtechwire.com/id-tech-digest-november-4-2026/>) — Published 2026-11-04

Singapore's IMDA is reportedly exploring, with GoDaddy, Cloudflare and Google, whether DNS could identify AI agents. That would give the internet's 1983 phone book a second job checking IDs at the door. Every ops person already knows where the postmortem will land: it's always DNS.

- **Meta Buys Conductor, Cloud Users Get Notice** — [Source](<https://www.axios.com/2026/11/04/meta-acquires-ai-coding-startup-conductor>) — Published 2026-11-04

Meta bought Conductor, the app for running several coding agents in parallel, and the team is joining Meta Superintelligence Labs. Terms weren't disclosed. Conductor Cloud goes read-only Nov. 13 and shuts off Nov. 20. The local app gets model updates and critical fixes until early 2027. Conductor ran agents from rival labs too, so everyone wants to know whether that survives the move.

- **OpenAI Shops Too: Pierre Computer** — [Source](<https://www.axios.com/2026/11/04/meta-acquires-ai-coding-startup-conductor>) — Published 2026-11-04

Not to be outdone, OpenAI told Axios it plans to buy Pierre Computer, which stores and manages AI-generated code. It's OpenAI's second coding pickup after the Ona deal announced in June. Agents are producing mountains of code nobody typed by hand, and someone has to keep track of it. OpenAI would like to be that someone.

- **Kimi K3.1 Pro Weights Drop: Bring Disks** — [Source](<https://huggingface.co/moonshotai/Kimi-K3.1-Pro>) — Published 2026-11-04

Moonshot launched Kimi K3.1 Pro in October, and today the open weights landed on Hugging Face. It has 2.8 trillion parameters with 104B active, and reportedly ships as 96 shards totaling about 1.56 TB under a custom non-OSI licence. Self-hosting starts with a purchase order for storage. Before the release, Artificial Analysis said it would cut the gap between open and proprietary models from 12 points to 3.

- **Ripple-65B Crowns Itself America's Coding Champ** — [Source](<https://www.ricursive.com/ripple>) — Published 2026-11-04

Ricursive calls its Ripple-65B Preview "U.S. Open-Weight SOTA on Agentic Coding," meaning best in its class. That's the company grading its own homework. The "U.S." qualifier is carrying extra weight today, since a Chinese lab just released 1.5 terabytes of open weights.

- **Go Gets a Brand-New JSON API** — [Source](<https://go.dev/blog/jsonv2>) — Published 2026-11-04

The Go team introduced encoding/json v2, a new official JSON API, and Gophers have plenty to say about it. Nearly every Go service reads or writes JSON somewhere, so a second version of the standard package lands on the desk of anyone shipping APIs.

- **Apple Puts Engineers on an AI Diet** — [Source](<https://www.macrumors.com/2026/11/04/apple-reducing-employee-ai-spending/>) — Published 2026-11-04

Bloomberg reports that in October, Apple cut some engineers' daily AI spend caps from $300 to $200. Some could drop to $100, and certain non-engineering teams could be capped at $25. Some teams are being nudged toward cheaper or on-device models. The punchline: few people ever hit $300, and Apple's R&D rose 32% in fiscal 2026.

- **Texas Voted, and Data Centers Flinched** — [Source](<https://www.cnbc.com/2026/11/04/ai-stocks-texas-governor-data-centers.html>) — Published 2026-11-04

Last brief, the data center backlash was winning local ballot fights. Now it has the Texas governor's mansion, in a state holding 25%+ of planned US capacity. Gina Hinojosa ran on an immediate moratorium, tougher water and power rules, and no tax breaks, and AI data center stocks fell on the result. GLJ Research says about 13 GW is exposed. Altimeter's Brad Gerstner says 10–15 GW might never get built. Abbott had already paused permits. Musk, who spent big on the losing side, now likes "data centers in space."

- **Big Tech Pulls Out the AI Credit Card** — [Source](<https://finance.yahoo.com/markets/stocks/articles/stock-market-news-nov-4-132500586.html>) — Published 2026-11-04

Oracle filed to sell $20B of new stock and bonds for its AI buildout, and Meta is seeking about $25B in bonds. The timing is bold. They're raising money to build on the same day the state with the most planned capacity elected a governor who ran on a moratorium.

- **ChatGPT Search Is 20% of Google's?** — [Source](<https://www.bigtechnology.com/p/openai-chatgpt-search-is-about-20>) — Published 2026-11-04

OpenAI's Adam Fry said Monday that ChatGPT search volume is about 20% of Google's, and that weekly users reportedly went from 1B to 1.2B in 60 days. Check the counting rules first. Any prompt that triggers a web search counts, and OpenAI didn't disclose the Google baseline or its method. Ahrefs puts ChatGPT at 0.36% of web referral traffic.

- [Lebanon's Two Clocks and the Question Calendars Don't Ask](<https://current.tinyfish.ai/issue/10/echoes/article/57651/markdown>) — Published 2026-10-30

On March 26, 2023, Lebanon woke up on two clocks. The caretaker government had postponed daylight saving three days earlier. Churches and TV channels moved forward anyway, government offices stayed put, and most phones jumped on their own. Middle East Airlines printed every departure an hour earlier, so its planes still left at the same moment. That week made each calendar show what it had been storing: an exact instant, or a time on the wall that politics can move. Software assistants now make that choice without asking anyone.

- [Faria Huq and the Reason Behind a Human Step](<https://current.tinyfish.ai/issue/10/practitioners-corner/article/57548/markdown>) — Published 2026-10-30

When a person takes control from an AI agent driving their web browser, the system records a human step, but not why. Faria Huq and her Carnegie Mellon collaborators have built tools around these moments: an agent that can't find the right forum, a shopper who realized the brand mattered only after seeing the agent's pick. Their system learns to predict when someone will step in. The reason it sets aside would tell a team whether to fix the agent, the website, or its understanding of the person.

- [Your Agent's Questions Need a Recipient and a Timer](<https://current.tinyfish.ai/issue/10/foundations/article/57518/markdown>) — Published 2026-10-30

When an AI agent stops mid-task to ask a human something, it often reads as a failure of autonomy. In one study, letting coding agents ask about bug reports stripped of key details won back most of the lost ground, lifting solve rates from about 55% to 69.4%. But the "human" answering was another model, holding the full report and standing by. Real people are in meetings, or asleep. The design work is in the ask: who gets it, what it says, and what happens while it waits.

- [Who Pays While the Agent Waits](<https://current.tinyfish.ai/issue/10/market-pulse/article/57577/markdown>) — Published 2026-10-30

Google's new service for hosting AI agents starts from a fact anyone who has watched one run already knew: most of the time, the agent is waiting, for the model to answer or for a person to reply. So Google suspends idle agents and promises you won't pay for idle machines. Fair enough, but the wait still gets paid for. It moves into approval queues nobody times, and then onto the plan, which comes back exactly as it left, even if the stock it counted on has since sold.

### [Market Pulse](<https://current.tinyfish.ai/issue/10/market-pulse/markdown>)

Reading the agent ecosystem through a practitioner's lens

- [Payment Networks Just Solved Agent Authentication at Scale](<https://current.tinyfish.ai/issue/10/market-pulse/article/7315/markdown>) — By [Nora Kaplan](<https://current.tinyfish.ai/team/26/markdown>) · Published 2025-12-31 · Format: The Signal

An agent completes a purchase on one merchant site, then gets blocked on another for doing exactly what it was instructed to do. The fraud detection system can't distinguish authorized automation from credential stuffing—and across hundreds of vendor sites, this problem multiplies.

- [Pricing Chaos Reveals Where Agent Value Will Settle](<https://current.tinyfish.ai/issue/10/market-pulse/article/7250/markdown>) — Published 2025-12-31

December brought three wildly different pricing models from major vendors. Salesforce charges $2 per conversation, plus separate per-lead fees and credit systems. Microsoft bills $4 per hour. Intercom wants $0.99 per resolution.

- **The Multi-Agent Performance Cliff** — [Source](<https://arxiv.org/abs/2512.08296>) — Published 2025-12-31

Google and MIT researchers tested 180 multi-agent configurations and found the inflection point: beyond 45% single-agent accuracy, adding more agents degrades performance. Tool-heavy environments suffer worst, with efficiency penalties reaching 6×. Centralized coordination helps parallel tasks; sequential workflows need different architecture entirely.

- **Where to Spend Your Adaptation Budget** — [Source](<https://arxiv.org/abs/2512.08296>) — Published 2025-12-31

Stanford, Harvard, Berkeley, and Caltech teams mapped adaptation strategies along two axes: what you adapt (agent versus tools) and what drives updates (execution feedback versus outcome metrics). Their framework shows most production systems win by keeping base models stable while adapting tools frequently.

- **Escaping the Reflexion Loop** — [Source](<https://arxiv.org/html/2512.20845>) — Published 2025-12-31

Researchers identified degeneration-of-thought in single-agent Reflexion, where agents rehearse the same flawed reasoning across iterations. Multi-Agent Reflexion uses structured debate among persona-based critics to generate richer reflections, guiding strategy improvements without parameter updates. Particularly valuable for web agents recovering from navigation dead ends.

- **Prompt Design as Cooperation Architecture** — [Source](<https://arxiv.org/abs/2512.07462>) — Published 2025-12-31

Extended FAIRGAME framework reveals linguistic framing shapes agent cooperation as much as architecture does. Models show incentive-sensitive cooperation patterns, cross-linguistic divergence, and systematic defection as tasks near completion. Language effects rival architectural differences in magnitude when agents coordinate on shared resources.

- **OpenTelemetry Tackles Agent Observability** — [Source](<https://opentelemetry.io/blog/2025/ai-agent-observability/>) — Published 2025-12-31

The GenAI group is standardizing telemetry for IBM Bee, CrewAI, AutoGen, LangGraph. Schema work nobody celebrates. But it means you can switch frameworks without rebuilding your entire monitoring stack. That's the kind of boring that saves months.

- **Observability Tools You Can Actually Own** — [Source](<https://www.firecrawl.dev/blog/best-llm-observability-tools>) — Published 2025-12-31

Langfuse and OpenLLMetry hit production grade. MIT-licensed, self-hostable, integrate with your existing APM. No vendor negotiations when you need to scale. No surprise bills when traffic spikes. Just infrastructure that works how infrastructure should.

- **vLLM Borrows From Operating Systems** — [Source](<https://www.koyeb.com/blog/best-llm-inference-engines-and-servers-to-deploy-llms-in-production>) — Published 2025-12-31

Berkeley's PagedAttention applies virtual memory concepts to attention algorithms. Twenty-four times faster than HuggingFace Transformers. Not a new model architecture. Just computer science fundamentals applied to serving at scale. Unglamorous and essential.

- **Agent Schemas Cut Integration Work** — [Source](<https://fabrix.ai/blog/some-of-the-open-source-standards-used-with-ai-agents-or-agentic-frameworks/>) — Published 2025-12-31

Open Agentic Schema Framework standardizes how agents describe capabilities and interact. Teams report 40-60% less integration work versus custom implementations. The standardization nobody wants to build but everyone needs when connecting multiple systems.

- **Anthropic: Simple Code Beats Complex Frameworks** — [Source](<https://www.anthropic.com/research/building-effective-agents>) — Published 2025-12-31

After working with dozens of production teams, Anthropic found a pattern. Successful implementations use composable building blocks. Teams strip out abstraction layers as they move to production. Direct code wins. Not the answer anyone wanted, but it's what works.

- **Infrastructure-as-Code Reaches Model Serving** — [Source](<https://www.qwak.com/post/building-llm-applications-for-production>) — Published 2025-12-31

Terraform and CI/CD for LLM deployments. Version-controlled environments, auditable changes, trivial rollbacks. Staging that actually mirrors production. Classic DevOps discipline finally applied to model serving. Boring in the best possible way.

- **Google Introduces Context Engineering as Production Agent Discipline** — [Source](<https://developers.googleblog.com/architecting-efficient-context-aware-multi-agent-framework-for-production/>) — Published 2025-12-31

Context as compiled infrastructure rather than prompt gymnastics. Systems engineering returns to agent development. About time someone said it.

- **Visa and Mastercard Build Payment Rails for Agent Commerce** — [Source](<https://www.cnbc.com/2025/12/29/ai-agentic-shopping-price-discounts-cheap-sales-commerce-visa-mastercard-chatbots.html>) — Published 2025-12-31

Cryptographic authentication for bot transactions solves identity problems. Liability for agent mistakes stays gloriously undefined. Infrastructure always arrives before use cases.

- **Enterprise Agent Pilots Double, But Production Deployment Stays Flat** — [Source](<https://gigster.com/blog/why-your-enterprise-isnt-ready-for-agentic-ai-workflows/>) — Published 2025-12-31

Pilots jumped from 37% to 65% in one quarter. Production deployment? Still 11%. The demo-to-deployment gap gets its numbers.

- **LangChain Publicly Recommends LangGraph for Agent Orchestration** — [Source](<https://medium.com/@hieutrantrung.it/the-ai-agent-framework-landscape-in-2025-what-changed-and-what-matters-3cd9b07ef2c3>) — Published 2025-12-31

Framework consolidation accelerates. CrewAI at 60% of Fortune 500, LangGraph in production at 400 companies. Chaos resolving into architectural clarity.

- **Agent Observability Overhead Measured at 12-15 Percent** — [Source](<https://research.aimultiple.com/agentic-monitoring/>) — Published 2025-12-31

AgentOps and Langfuse benchmark actual performance costs. Monitoring carries real overhead, but production systems need it anyway. Table stakes territory.

- **Financial Services Contract Review Drops from $48 to 32 Cents** — [Source](<https://pub.towardsai.net/building-production-grade-ai-agents-in-2025-the-complete-technical-guide-9f02eff84ea2>) — Published 2025-12-31

Real production numbers: 150x cost reduction, 30x speed improvement, 9% accuracy gain. Infrastructure costs stay material despite token economics improving.

### [Foundations](<https://current.tinyfish.ai/issue/10/foundations/markdown>)

Conceptual clarity earned from building at scale

- [Quality Degradation Curves](<https://current.tinyfish.ai/issue/10/foundations/article/7218/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2025-12-31 · Format: Field Guide

Your hotel pricing extraction ran at 98% success for six months. Then it didn't. Quality rarely breaks all at once—it erodes. Operating web agents across thousands of sites, you start seeing patterns in how that erosion happens. Some automations cliff overnight when sites change. Others drift downward so gradually you don't notice until you're deep in the hole. The shape of degradation reveals infrastructure capability better than any demo. Understanding these curves matters before you're locked into an approach.

- [When Developers Need to See What's Actually There—The Cookies.txt Browser Extension](<https://current.tinyfish.ai/issue/10/foundations/article/7221/markdown>) — By [Nora Kaplan](<https://current.tinyfish.ai/team/26/markdown>) · Published 2025-12-31 · Format: Tools in Context

Three hours into debugging, you discover the session expired mid-workflow. Figuring that out meant adding logging, rerunning scripts, parsing DevTools. What you needed was simpler: just look at the cookies. Development teams install the Cookies.txt browser extension for this moment. Click the icon, export, open the file. Authentication tokens, expiration timestamps, domain coverage—all visible. No parsing, no code. When iteration speed matters more than automation, seeing what's actually there beats scripting it.

- [When Teams Need Sessions That Survive Restarts—Selenium's Cookie API](<https://current.tinyfish.ai/issue/10/foundations/article/7222/markdown>) — By [Nora Kaplan](<https://current.tinyfish.ai/team/26/markdown>) · Published 2025-12-31 · Format: Tools in Context

Test suites that authenticate fresh for every run waste minutes multiplied across hundreds of cases. Automation workflows that break when tokens expire mid-execution lose reliability at scale. Production web agents can't rely on manual cookie extraction—sessions must persist across thousands of runs without human intervention. Teams building at this scale implement Selenium's Cookie API, where code saves authentication state to files and reloads it automatically. When workflows run in CI/CD pipelines, programmatic session management stops being optional.

- [Agents Keep Running Out of Context Mid-Task](<https://current.tinyfish.ai/issue/10/foundations/article/7224/markdown>) — Published 2025-12-31

We're watching companies hit the same wall. Agents start complex tasks, run out of context halfway through, leave work half-finished. Anthropic documented this clearly: even frontier models exhaust their context windows mid-project, forcing the next session to reconstruct what happened.

- **What Breaks Between Demo and Month Three?** — [Source](<https://medium.com/@mxcruzel/ai-agents-in-production-why-the-demo-doesnt-match-reality-4d929860c156>) — Published 2025-12-31

Demos run on controlled inputs. Production brings unexpected file formats, unsupported languages, creative ways to break workflows. Edge cases become daily occurrences. Users behave unpredictably. The carefully designed happy path meets reality, and you discover what actually breaks at scale.

- **Does This Fade Into Infrastructure?** — [Source](<https://www.salesforce.com/blog/ai-agent-maintenance/>) — Published 2025-12-31

Some systems run quietly in the background. Others demand constant prompt tweaking, model retraining, manual intervention. Maintenance costs run 30-50% of development annually. Will this become invisible infrastructure? Or will it require a dedicated team just to keep running?

- **Can You Set a Ceiling on Costs?** — [Source](<https://skooloflife.medium.com/why-95-of-enterprise-ai-projects-fail-the-architecture-problem-nobody-wants-to-admit-fd79967567d8>) — Published 2025-12-31

Agents enter infinite loops with no error states. They appear normal while racking up token charges. Without depth counters, visited-node tracking, explicit budget controls, costs scale unpredictably. You discover problems through monthly bills, not monitoring dashboards.

- **Does This Work With Actual Systems?** — [Source](<https://composio.dev/blog/why-ai-agent-pilots-fail-2026-integration-roadmap>) — Published 2025-12-31

Enterprise environments have undocumented rate limits, brittle middleware, custom fields, duplicate logic. Agents tested against clean APIs struggle with real infrastructure. Your organization's actual complexity looks nothing like the idealized systems vendors assume exist.

- **Can You See What Went Wrong?** — [Source](<https://ashutoshtripathi.com/2025/12/01/ai-agent-performance-evaluation-a-production-engineers-guide/>) — Published 2025-12-31

Agents produce correct outputs through incorrect processes. Silent failures where results look right but execution failed. Without full interaction traces, reasoning logs, tool call visibility, you can't debug production issues. You see that something broke, not what the agent was thinking.

- **Where Does Automation End and Judgment Begin?** — [Source](<https://www.diagrid.io/blog/building-production-ready-ai-agents-what-your-framework-needs>) — Published 2025-12-31

Agents lack judgment about which decisions need human approval. They confidently execute high-stakes actions without understanding business impact. Human-in-the-loop isn't a fallback. Which decisions require oversight? How do you enforce those boundaries?

- [An Interview with The Handshake](<https://current.tinyfish.ai/issue/10/foundations/article/7223/markdown>) — Published 2025-12-31

We meet The Handshake in what can only be described as a state of professional exhaustion. For decades, it has been the invisible diplomat of the internet—the split-second negotiation that happens every time your browser connects to a website. Originally designed to establish secure, encrypted connections, The Handshake now finds itself in an uncomfortable position: being meticulously analyzed, catalogued, and used to identify users with surprising precision.

### [Practitioner's Corner](<https://current.tinyfish.ai/issue/10/practitioners-corner/markdown>)

Lessons from the field—what we see building at scale

- [How Three Retries Become Sixty-Four Database Attempts](<https://current.tinyfish.ai/issue/10/practitioners-corner/article/7268/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2025-12-31 · Format: Field Dispatch

Error rates double every thirty seconds—4%, 8%, 16%, 32%—while every recovery system reports normal behavior. Frontend shows three retry attempts per failure. API gateway executes its own retry logic. Backend service follows documented procedures. Yet one failed authentication becomes sixty-four database attempts before any layer notices. When we're running thousands of concurrent sessions, this pattern appears constantly: systems designed to provide resilience somehow amplifying failures exponentially instead.

- [Kate Blair and the Quest to Build HTTP for Agent Coordination](<https://current.tinyfish.ai/issue/10/practitioners-corner/article/7269/markdown>) — By [Nora Kaplan](<https://current.tinyfish.ai/team/26/markdown>) · Published 2025-12-31 · Format: Builder Profiles

When Tyson Foods and Gordon Food Service deployed AI agents to manage supply chain operations, they discovered something almost quaint: the agents couldn't talk to each other. Custom point-to-point integration was the only option. Exactly the kind of brittle solution that breaks when you're coordinating across dozens of suppliers.

- [97% of Traffic Disappeared After Bot Detection](<https://current.tinyfish.ai/issue/10/practitioners-corner/article/7270/markdown>) — Published 2025-12-31

OffenderWatch processed 80 million API requests daily. After implementing rate limiting and bot protection, that number dropped to 2.5 million. A 97% reduction.

- **Cloudflare WAF Buffer Triggers 25-Minute Outage** — [Source](<https://blog.cloudflare.com/5-december-2025-outage/>) — Published 2025-12-31

Cloudflare increased WAF buffer size from 128KB to 1MB on December 5 while patching CVE-2025-55182. The change failed, impacting 28% of HTTP traffic for 25 minutes. Second major outage in under a month. Company response: "Code Orange: Fail Small."

- **React2Shell Exploited Hours After Disclosure** — [Source](<https://aws.amazon.com/blogs/security/china-nexus-cyber-threat-groups-rapidly-exploit-react2shell-vulnerability-cve-2025-55182/>) — Published 2025-12-31

China state-nexus groups exploited CVE-2025-55182 within hours of December 3 disclosure. One threat cluster spent nearly an hour troubleshooting exploitation attempts. AWS Sonaris processes 200 billion events per minute detecting real-time exploitation patterns.

- **Trust Wallet Extension Loses $7M via Leaked Key** — [Source](<https://thehackernews.com/2025/12/trust-wallet-chrome-extension-bug.html>) — Published 2025-12-31

Attacker used leaked Chrome Web Store API key to publish malicious Trust Wallet extension v2.68 on December 24. One million users affected, $7 million in losses. Attacker registered exfiltration domain December 8, began requests December 21.

- **Google ADK Treats Context as Compiled View** — [Source](<https://developers.googleblog.com/architecting-efficient-context-aware-multi-agent-framework-for-production/>) — Published 2025-12-31

Google Agent Development Kit documentation shows model cost and time-to-first-token grow quickly with context size. Framework treats context as compiled view over stateful system, distinguishing durable state (Sessions) from per-call views (working context).

- **Microsoft's 50-Agent System Shows Bimodal Results** — [Source](<https://techcommunity.microsoft.com/blog/appsonazureblog/context-engineering-lessons-from-building-azure-sre-agent/4481200>) — Published 2025-12-31

Azure SRE Agent team's multi-agent system with 50+ sub-agents produced bimodal results: when handoffs worked, everything worked. When they failed, agents got lost. Poorly tuned sub-agents pollute orchestrator context with confused outputs, causing infinite loops.

- **Docker Hardened Images Cut Vulnerabilities 95%** — [Source](<https://www.docker.com/press-release/docker-makes-hardened-images-free-open-and-transparent-for-everyone/>) — Published 2025-12-31

Docker announced December 17 that Hardened Images reduce vulnerabilities up to 95% using distroless runtime. Docker Hub handles 20 billion pulls monthly. Extending hardening to MCP server images as supply chain attacks projected to cost $60 billion in 2025.

- **OpenAI's Telemetry Cascade: When Observability Kills Availability** — [Source](<https://status.openai.com/incidents/01JMYB483C404VMPCW726E8MET>) — Published 2025-12-31

Four-hour outage from metrics deployment. Watch how telemetry volume can overwhelm the systems it's meant to monitor.

- **GenAI Governance: IBM's $4.45M Lesson in Codified Controls** — [Source](<https://dev.to/dee66/the-production-ready-genai-platform-a-complete-aws-architecture-for-codified-governance-4m5e>) — Published 2025-12-31

Vector poisoning losses documented. AWS architecture showing why governance needs enforcement in code, not policy documents.

- **Data Engineering 2024: PayPal's Spark 3 Migration Math** — [Source](<https://www.dataengineeringweekly.com/p/the-state-of-data-engineering-in>) — Published 2025-12-31

70% cost reduction from version upgrade and GPU optimization. Includes Medium's pipeline work and Expedia's SLO platform.

- **Data Center Buildout: 80 GW by 2030** — [Source](<https://www.mckinsey.com/industries/private-capital/our-insights/scaling-bigger-faster-cheaper-data-centers-with-smarter-designs>) — Published 2025-12-31

McKinsey's infrastructure projections with cooling trade-offs. Know the power constraints before you plan for scale.

- **Uber's Distributed Systems: P99 Latency Over Averages** — [Source](<https://blog.pragmaticengineer.com/operating-a-high-scale-distributed-system/>) — Published 2025-12-31

Production monitoring practices from actual scale. Alert management and on-call sustainability that survives real operations.

- **Engineering Blogs Worth Following: LinkedIn's 4 Trillion Events** — [Source](<https://betterstack.com/community/blog/cto-blogs/>) — Published 2025-12-31

Curated list of company engineering blogs. LinkedIn's Kafka and Pinot work shows what billion-user infrastructure actually requires.

### [Echoes](<https://current.tinyfish.ai/issue/10/echoes/markdown>)

Past infrastructure decisions echoing in today's production realities

- [How TCP Saved the Internet and Complicated Everything After](<https://current.tinyfish.ai/issue/10/echoes/article/7284/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2025-12-31 · Format: Infrastructure Inflections

Spin up a few thousand concurrent browser sessions and you'll hit a wall that feels arbitrary: ports exhaust, connections pile up in limbo, your infrastructure can't establish new sessions even though bandwidth looks fine. The operational puzzle isn't resource limits—it's something deeper.

- [When Schema Freedom Became Maintenance Prison](<https://current.tinyfish.ai/issue/10/echoes/article/7285/markdown>) — Published 2025-12-31

MongoDB and Redis arrived in 2009 promising escape from SQL's rigid schemas. Web 2.0 companies drowning in data grabbed the lifeline. No more schema migrations. No more JOIN complexity. Just store JSON and scale horizontally forever.

- **Coordination Breaks Before Systems Do** — [Source](</echoes/complexity-outpaces-coordination>) — Published 2025-12-31

At two hundred engineers, pull requests queue for days. Features need five conversations before shipping. The systems still work. The organization doesn't. You're not building too slowly. You're coordinating through structures designed for twenty people.

- **Each Generation Reaches Scale Faster** — [Source](</echoes/adoption-cycle-compression>) — Published 2025-12-31

Personal computers needed sixteen years to reach mainstream adoption. Internet took seven. Smartphones, five. ChatGPT hit one hundred million users in two months. The pattern holds across every infrastructure generation: penetration velocity keeps accelerating.

- **Inference Workloads Overtook Training Compute** — [Source](</echoes/inference-workload-dominance>) — Published 2025-12-31

In 2023, inference consumed one-third of AI compute. Now it's two-thirds. Training stays concentrated in massive clusters. Inference fragments across specialized hardware everywhere. Watch where the actual computational work migrates during technology maturation.

- **Early Architecture Choices Echo for Years** — [Source](</echoes/boundary-decisions-echo>) — Published 2025-12-31

Service boundaries drawn at twenty engineers still constrain teams at two hundred. Components that map cleanly to single teams scale smoothly. Those that don't require cross-team negotiation for every deployment. Your earliest architecture decisions determine growth capacity long after you've forgotten making them.

- **Distribution Multiplies Configuration Risk Exponentially** — [Source](</echoes/configuration-cascade-risk>) — Published 2025-12-31

Kubernetes and service meshes expand configuration surface area across clusters. One RBAC mistake opens backdoors everywhere. A single overlooked network policy cascades into system-wide incidents. Distribution transforms simple configuration errors into infrastructure-wide failures.

- **Cloud-Native Architecture Intensifies Cost Pressure** — [Source](</echoes/cloud-native-cost-complexity>) — Published 2025-12-31

Infrastructure-as-code makes spinning up resources trivial. Cloud-native layers add complexity monoliths never faced. Highly dynamic environments become harder to meter accurately. As adoption grows, cost management shifts from afterthought to primary operational concern.

- **MapReduce Made Distributed Computing Accessible to Ordinary Programmers** — [Source](<https://research.google.com/archive/mapreduce-osdi04.pdf>) — Published 2025-12-31

Jeffrey Dean and Sanjay Ghemawat's 2004 paper automated parallelization, fault tolerance, and scheduling across thousands of machines. Programmers wrote simple map and reduce functions; the system handled distribution. By 2006, Google processed twenty petabytes daily through 100,000 MapReduce jobs. Hadoop, Spark, and modern batch processing descended directly from this model.

- **CAP Theorem Formalized the Impossible Trade-offs in Distributed Systems** — [Source](<https://groups.csail.mit.edu/tds/papers/Gilbert/Brewer2.pdf>) — Published 2025-12-31

Eric Brewer conjectured in 2000 what Gilbert and Lynch proved in 2002: distributed systems cannot simultaneously guarantee consistency, availability, and partition tolerance. Pick two. Every NoSQL database since has been a choice about which property to sacrifice. MongoDB chose consistency. Cassandra chose availability. Both accepted partition tolerance as inevitable.

- **REST Was Designed for Hypermedia, Became the API Standard** — [Source](<https://ics.uci.edu/~fielding/pubs/dissertation/top.htm>) — Published 2025-12-31

Roy Fielding's 2000 dissertation described architectural constraints for distributed hypermedia systems while co-authoring HTTP specifications. Mid-2000s developers, desperate for SOAP alternatives, repurposed REST for web APIs. Fielding never intended this. Every stateless API inherits constraints designed for browsers navigating linked documents, not microservices exchanging JSON.

- **Paxos Provided the First Correct Consensus Protocol for Distributed Systems** — [Source](<https://lamport.azurewebsites.net/pubs/paxos-simple.pdf>) — Published 2025-12-31

Leslie Lamport discovered Paxos in the late 1980s. Reviewers found his parliament analogy too obscure for eight years until 1998 publication. The algorithm now powers Google Chubby, Spanner, and Megastore; Microsoft Autopilot; Amazon DynamoDB; Cassandra transactions. Distributed consensus became possible because Lamport proved correctness mathematically.

- **AI Workloads Collide With Pre-Pandemic Cloud Architecture** — [Source](<https://www.deloitte.com/us/en/insights/topics/technology-management/tech-trends/2026/ai-infrastructure-compute-strategy.html>) — Published 2025-12-31

Multicloud strategies from 2019 assumed web traffic patterns. AI's compute hunger exposes those assumptions daily.

- **Database Architecture's Eternal Return: Stonebraker and Pavlo Trace Patterns** — [Source](<https://blocksandfiles.com/2024/09/06/database-architecture-paper/>) — Published 2025-12-31

MIT and Carnegie Mellon professors map how 1960s text search engines prefigured today's vector databases.

- **Microservices' 2010s Promise Created Today's API Management Crisis** — [Source](<https://www.postman.com/state-of-api/2025/>) — Published 2025-12-31

Netflix and Amazon's architectural wins spawned API sprawl. Ninety-three percent of teams still struggle with collaboration.

- **REST's Twenty-Year Legacy Constrains Event-Driven Architecture** — [Source](<https://www.techtarget.com/searchapparchitecture/tip/Whats-next-for-APIs-API-trends>) — Published 2025-12-31

Fielding's 2000 dissertation solved request-response elegantly. Streaming data reveals what REST never anticipated.

- **Serverless Cold Starts: Consequence of Abstracting Infrastructure Away** — [Source](<https://247labs.com/serverless-architecture-in-2025/>) — Published 2025-12-31

The journey from bare metal through containers built initialization latency into serverless. Physics remains undefeated.

- **Edge Computing Rediscovers CDN-Era Distribution Challenges** — [Source](<https://cloud.google.com/blog/topics/hybrid-cloud/edge-computing-architectural-challenges-and-pitfalls>) — Published 2025-12-31

Pushing compute to disconnected devices resurrects problems CDN architects solved differently. Reliable connectivity remains aspirational.

### [Vision](<https://current.tinyfish.ai/issue/10/vision/markdown>)

Where human-AI collaboration is heading

- [When Your Vocabulary Starts Lying to You](<https://current.tinyfish.ai/issue/10/vision/article/7234/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2025-12-31 · Format: Threshold Moments

The first time it happens, you think it's a bug. Your team is explaining a production failure, and the words everyone's using sound right but generate completely wrong intuitions about what actually broke. "Session timeout." "Restart the run." "Isolated failure."

- [The Predictability Premium](<https://current.tinyfish.ai/issue/10/vision/article/7235/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2025-12-31 · Format: Infrastructure Economics

Managed authentication services charge $500,000 annually. Building custom infrastructure costs $50,000 upfront. The arithmetic seems obvious—until a security incident cascades across thousands of sites, triggering compliance reviews, helpdesk floods, and engineering escalations that multiply faster than spreadsheets capture. The expensive option becomes cheaper through what it prevents. But when does predictability justify its premium, and when does it just mean paying more for the same outcome?

- [When Scale Inverts Economics](<https://current.tinyfish.ai/issue/10/vision/article/7236/markdown>) — By [Rina Takahashi](<https://current.tinyfish.ai/team/25/markdown>) · Published 2025-12-31 · Format: Infrastructure Economics

Traditional infrastructure gets cheaper at scale. Web automation against bot detection does the opposite. The lightweight scraper multiplies bandwidth costs. The efficient proxy gets blocked, forcing expensive alternatives. Optimization strategies that should reduce unit costs actually compound them through detection complexity and infrastructure depth that pricing pages never show. Scale that should provide leverage increases costs instead. The cheap option becomes exponentially expensive through patterns only visible at production scale.

- [Mino the Web Agent on Fighting Systems Designed to Stop Them](<https://current.tinyfish.ai/issue/10/vision/article/7237/markdown>) — Published 2025-12-31

Every enterprise web agent operates in a peculiar paradox: they're legitimate automation navigating infrastructure specifically designed to stop automation. It's like being invited to a party where the bouncer has been trained to keep you out.

- **Who Takes the Fall?** — [Source](<https://medium.com/@akitrablog/accountability-and-liability-in-agentic-ai-systems-navigating-legal-and-ethical-challenges-339353af886d>) — Published 2025-12-31

Autonomous systems fail. Humans absorb the blame. Engineers, operators, users become accountable for decisions they never controlled, buried in reasoning they can't access. Researchers call these "moral crumple zones." The accountability gap widens as agents gain autonomy. Someone always pays.

- **What Dies When Agents Live?** — [Source](<https://www.cyberark.com/resources/blog/crash-hack-deviate-three-ai-agent-failures-every-enterprise-must-prepare-to-face>) — Published 2025-12-31

Step out of a workflow long enough and the muscle memory vanishes. Manual backups become folklore. Resilience erodes quietly until automation breaks and reveals how much you've outsourced. What happens to institutional knowledge when nobody remembers how things actually work?

- **Can You Fix What's Hidden?** — [Source](<https://openmetal.io/resources/blog/operational-visibility-is-reliability/>) — Published 2025-12-31

Invisible infrastructure means debugging with half the information. You can't establish accurate service levels or distinguish code errors from infrastructure contention. Incident response becomes guesswork. How do you maintain reliability when the foundation itself refuses to show its work?

- **Secure Execution, Flawed Reasoning?** — [Source](<https://arxiv.org/html/2505.09757>) — Published 2025-12-31

Blockchain guarantees tamper-resistant execution. The AI agent itself still hallucinates, carries biases, misaligns. Locking flawed reasoning in secure enclaves might amplify harm rather than contain it. Can you build trustless infrastructure around fundamentally unreliable intelligence?

- **Does Enthusiasm Count as Preparation?** — [Source](<https://www.ey.com/en_us/newsroom/2025/10/new-ey-survey-reveals-majority-of-workers-are-enthusiastic-about-agentic-ai-but-leadership-gaps-in-communication-and-lack-of-training-threaten-impact>) — Published 2025-12-31

Eighty-four percent of employees embrace agentic AI. Seventy-three percent don't understand how it affects their work. Only fifteen percent of organizations have actually deployed it. The gap between optimism and readiness threatens to stall transformation before it starts.

- **How Do You Stop Normal?** — [Source](<https://www.cyberark.com/resources/blog/crash-hack-deviate-three-ai-agent-failures-every-enterprise-must-prepare-to-face>) — Published 2025-12-31

Every enterprise deploying agents needs a kill switch. But a kill switch without detection is theater. Compromised agents often look like they're just doing their job. How do you halt what you can't distinguish from routine operation?

- **Optimal Human-AI Task Allocation: The 80/20 Framework** — [Source](<https://pubsonline.informs.org/doi/10.1287/mnsc.2024.05684>) — Published 2025-12-31

Management Science study reveals optimal configurations allocate 80% of human resources to the 20% most difficult tasks. AI automates easy work, augments humans on similar-performance tasks, while humans tackle high-uncertainty problems requiring innovation and judgment. Higher accuracy comes from strategic reallocation, not full automation.

- **Worker Attitudes Toward AI Automation Across 104 Occupations** — [Source](<https://futureofwork.saltlab.stanford.edu/>) — Published 2025-12-31

Stanford analyzed 1,500 workers finding 46.1% positive attitudes toward AI agent automation. Workers cite "freeing up time for high-value work" in 69.4% of cases. Research reveals competency shift from information-processing to interpersonal and organizational capabilities. Early 2025 data shows 36% of occupations already using AI for 25% of tasks.

- **The Agentic Web: From Human-Centric to Agent-Centric Internet** — [Source](<https://arxiv.org/html/2507.21206>) — Published 2025-12-31

July 2025 paper formally defines the Agentic Web as distributed ecosystem where autonomous agents plan, coordinate, and execute goal-oriented tasks. Web transforms from information retrieval platform to action-oriented framework where agents act on behalf of users. Outcomes replace page views as primary value metric.

- **Hidden Interfaces: Making Technology Disappear Into Materials** — [Source](<https://research.google/blog/hidden-interfaces-for-ambient-computing/>) — Published 2025-12-31

Google's ACM CHI research demonstrates displays embedded underneath textile, wood, and acrylic, achieving 5-40x brightness increases for simple shapes. Control surfaces visually disappear when inactive, appearing only when needed. Technical breakthrough advances ambient computing vision where technology coexists harmoniously with human environments rather than demanding attention.

## More

- [Publication guide](<https://current.tinyfish.ai/llms.txt>)
- [Issue archive](<https://current.tinyfish.ai/issues/markdown>)
