Guides name real columns, tables and owners.
Every guide points at real things in the catalog: the columns its SQL sums, the tables it reconciles against, the owner it says to ping. All of that keeps changing, and a guide has no way to notice on its own. So instaboard re-checks every guide against DataHub and pins each mismatch to the step it breaks.
This is that check running in the app. A month after the guide was recorded, validation comes back Out of date with four findings: the revenue column was renamed, the rollup table was deprecated, a freshness assertion started failing, and the person the guide says to ping no longer owns the table.
Each finding sits on the step that uses it, with the drift spelled out and a correction proposed. The same run writes back to DataHub, where the dataset gets a warning tag and an incident goes to its current owner.
Break it yourself below and watch the verdict change.