Build the ledger before you commission another governance dashboard
A polished control chart on untagged automation runs only accelerates the wrong debate.
Teams under pressure often skip ownership fields and jump to a new compliance board. Weeks later, risk and operations argue over different totals for the same pipeline because every job still shares one opaque service account.
Prefer policy and data-domain tags over UI widget names. Keep environment out of the job alias and in a property. Write allowed values the same day a new automation ships—or the path becomes a free-form dump.
In an Automation Governance Audit we spend early days on the inventory, not on chart cosmetics. Dashboards get sharper only after the ledger stops arguing with itself.