# Failure conditions in the record

_Published 2026-08-28._

Every case study on this site includes two sections that marketing pages usually omit: **failure conditions** and **current state**. They are not confessional. They are methodology.

## Why failure belongs in the record

A system that has never failed in a documented way is a system whose failure modes are unknown. Writing down the conditions under which the system breaks — the load it cannot handle, the inputs it misclassifies, the dependencies that take it down — is the only way to make those limits legible to the next person who has to operate or extend it.

Failure conditions are written as a table: the condition, the trigger, and the observed behavior. No narrative. The format forces specificity instead of a paragraph that says "the system is robust."

## What current state means

Current state is what the system is doing now, not what it was designed to do. A case study that ends at launch is incomplete. The current state section records whether the system is still in production, what it has been replaced by, or what it has grown into.

This is why the record is written to be read before the next engagement, not after. A reader who wants to understand how the studio works should be able to read the failure and current state sections and decide whether the approach is sound, not whether the launch was celebrated.