~/home/stream/teardowns

march 2026

what broke in a weekend agent test

a teardown of a promising workflow that failed once the edge cases and cleanup steps showed up.

the first version looked great in demos and fell apart in real usage.

the weak point was not the model output. it was all the surrounding state: filenames, retries, partial failures, and unclear ownership between steps.

teardowns are useful because they show where confidence was borrowed instead of earned.