Sure. But in that, the answer to "who owns this?" is Analytics. It's
Analytics who reached out and made sure everyone had a voice, it's
Analytics brainstorming, it's Analytics implementing it, it's
Analytics publicly logging it.

Again, ownership does not mean code reviewing everything or writing
anything. It means making sure things get factored in. That seems to
be what you're doing, here.

To be clear, ownership also means taking responsibility for problems. And what we're saying is that if those problems arise because of changes in other teams' code bases, we don't own that.