Freshness names that survive schema changes
Name the quality intent, not the table label—or the next rename breaks every pipeline report.
Teams often treat metric names as disposable labels. A warehouse rename ships, an engineer adds a staging hop, and suddenly rows_late and partition_delay both exist for the same moment. Quality reports that once looked clean become archaeological digs.
Prefer verbs that describe intent. Keep platform out of the event name—put it in a property so batch and streaming stay comparable during pipeline reviews. Write allowed properties on the same day you create the signal.
In Baseline engagements we spend the first day on inventory alone, because until synonyms are visible every later fix guesses at the wrong root.