When a Fix "Didn't Take," Suspect the Artifact, Not the Source

A common trap in automated content and document pipelines: you correct the underlying data or code, but the person on the other end still sees the old version. The instinct is to re-debug your logic. Usually the real culprit is a stale artifact — a cached render, an un-regenerated export, or a file that was never actually replaced.

Before touching the source again, confirm the exact output the recipient is looking at. Trace the chain from data to generation to delivery, and check whether the final artifact was rebuilt after your change. The gap is almost always at a boundary you assumed was automatic.

The broader lesson for anyone building generation pipelines: treat “the fix is in the code” and “the fix is in what the user sees” as two separate claims that each need verification. Build in a step that regenerates and re-checks the delivered artifact, not just the source of truth.

When possible, prefer capturing structured, richly-typed data over minimal fields at the point of collection — it’s far cheaper to shape rich data downstream than to reconstruct information you never captured.