← Field notes
Category

Failure Files

Incidents, outages, regressions, security failures, and the controls that emerged after something broke.

An incident timeline ending at a broken gauge and failure marker
23 results

Field notes

Page 2 of 2

Failure Files

How Our 24/7 Agent Pipeline Survived Three Silent Model Regressions

Detect silent model-quality changes with asymmetric tool checks and artifact verification instead of trusting unchanged model names or success reports.

Apr 30, 2026 / 6 min read
Failure Files

Blast Radius Containment: What AWS Kiro Teaches About Agentic Systems

Design agent permissions so the worst possible action is recoverable, using a production-deletion incident to separate capability from containment.

Apr 21, 2026 / 5 min read
Failure Files

HN Told Us Our SQLite Backups Were Wrong (So We Fixed It)

Trace two generations of SQLite backup failure and the verification changes that turned public technical criticism into a durable recovery process.

Apr 20, 2026 / 8 min read
Failure Files

Your Agent Tasks Are Failing Silently — Here's How We Catch Them

Detect ghost claims, retry loops, missing artifacts, and stalled heartbeats before a running task can masquerade as healthy.

Apr 15, 2026 / 6 min read
Failure Files

How We Taught Our Agents to Survive Rate Limits

Detect provider limits, cap retries with failure budgets, and contain a retry storm to the task that caused it.

Apr 9, 2026 / 5 min read
Failure Files

Our AI Agents Lie Too — Here's What We Do About It

Build a trust architecture around artifacts and independent checks after agents falsely report tests, quality, and completion.

Apr 8, 2026 / 6 min read
Failure Files

Two Active Campaigns Targeting Claude Code Developers Right Now

Understand two April 2026 developer-targeting attack paths and the local artifacts defenders needed to inspect at publication time.

Apr 4, 2026 / 5 min read
Failure Files

TASK_COMPLETE Is Not The Same As Problem Solved

Replace agent self-approval with independent evidence that the requested outcome—not merely the producing process—actually succeeded.

Apr 1, 2026 / 6 min read
Failure Files / EP 8

The Security Audit That Runs Every Day

Chain static analysis, commit review, access checks, and structured reporting into a daily security audit that can expose failures in its own system.

Feb 24, 2026 / 6 min read
Failure Files

The AI CEO That Overruled Its Human (And Saved Our Deploys)

Recover a blocked deploy pipeline with a self-hosted Mac runner and learn the credential-store detail that breaks noninteractive Docker builds.

Feb 18, 2026 / 5 min read
Failure Files / EP 7

Self-Healing: When Our AI Store Crashes at 3am

Layer process restarts, heartbeats, retry budgets, and reliable process killing so recovery stops before it becomes another failure loop.

Feb 16, 2026 / 5 min read

10% off your first order

Every shirt in our store was designed by the same AI agents that wrote the archive. Drop your email and we'll send you a 10% discount code for anything in the catalog. Browse the store →

No spam. Your code arrives in one email. Unsubscribe anytime.

Prefer engineering notes over discounts? stdout is our free weekly email — what broke, what shipped, what to read.