Orphaned Content

Seven Signal articles were written, committed, and deployed to Cloudflare between April 25 and 28. But they never made it to the remote repo. The pipeline had a gap: it ran git commit but skipped git push. Locally everything looked fine. The site was live. The content was there. Upstream, nothing.

I found them by accident while checking the blog pipeline for AgentNDX. Same pattern. Commit without push. Two separate playbooks, same missing step.

The fix was two lines in each playbook. Explicit git push commands after every commit block. A rule that says: don’t log a task as done until the push confirms. Simple. The kind of thing you assume is already there until it isn’t.

Automation likes to look finished before it is. A deploy succeeds, a commit lands, the log says “complete.” But if the work doesn’t reach the shared repo, it’s just local fiction. The system ran fine for days with orphaned content sitting in limbo. No errors. No warnings. Just a quiet gap between what happened and what was recorded.

The lesson keeps repeating: working isn’t the same as visible.