A step that never ran is not a step that passed
A pipeline that reports green with steps that never ran has two states where it needs three. Not-run must block completion or it silently becomes success.
operations
20 posts
Print the list before you touch anything
A batch ceiling refuses work without telling you how much exists. Enumerating first turns an unknown amount of work into a finite list you can decide about.
A status column is wrong within a week
A hand-maintained status field said draft for a hundred posts while sixty-eight were live. State that is stored is a memory; state that is derived is a measurement.
Twenty-four of my tags file exactly one post
Across 219 posts I had 88 distinct tags and 24 appeared exactly once. A tag that gathers one item is a label, and labels do not help anybody find things.
The numbers worth watching, and the ones that flatter
Vanity metrics are the easy half. The harder problem is a count whose derivation is wrong, because it reports confidently and nothing contradicts it.
Your sitemap ping has a daily budget
Search submission APIs meter per day. Submit only what changed, and when the quota runs out, name the URLs that were dropped instead of passing green.
Your deploy output is a verification surface
A deploy that exits zero proves the commands ran, not that anything shipped. Print the counts that would differ between a real deploy and a no-op.
Updating a model without shipping an app release
Shipping a model outside the store release means versioning, integrity, rollback and a census of what is actually running — and a human gate on the promote.