Auto-Governed Data Layer Evolution (SDR 2.0)

[#1]

Description
The Site Data Reference (SDR) is constantly evolving as new analytics needs come up. Right now, every change is handled manually — reviewing requests, mapping fields, and updating the schema one by one. It works, but it’s slow and makes it hard to keep different divisions aligned.

Why is this feature important to you
I’m responsible for tagging governance across multiple teams. The challenge is balancing speed with consistency. When requests pile up, there’s pressure to implement one-offs, which leads to fragmentation and extra rework later. Having a smarter way to spot repeat needs and streamline approvals would save a lot of time and prevent drift.

How would you like the feature to work
Ideally, the system could scan incoming requests, flag patterns that show up across teams, and propose new standardized fields for the SDR. From there, it should feed into an approval workflow so governance owners can decide what gets added. That way, divisions move faster but we still keep a single, trusted standard.

Current Behavior
At the moment, updates only happen when someone notices overlap and manually edits the SDR. There’s no automated way to surface common needs or manage approvals.