In the detailed explainer I see that IG uniqueness across all IGs joined by a browser, is determined by (owner, name) tuple:

The user agent has an interest group set, a [list](https://infra.spec.whatwg.org/#list) of [interest groups](https://wicg.github.io/turtledove/#interest-group) in which [owner](https://wicg.github.io/turtledove/#interest-group-owner) / [name](https://wicg.github.io/turtledove/#interest-group-name) pairs are unique.

9.4 in the list in that section seems to back that up:

If the browser is currently storing an interest group with owner and name that matches interestGroup, then set the [bid counts](https://wicg.github.io/turtledove/#interest-group-bid-counts), [join counts](https://wicg.github.io/turtledove/#interest-group-join-counts), and [previous wins](https://wicg.github.io/turtledove/#interest-group-previous-wins) of interestGroup to the values of the currently stored one and remove the currently stored one from the browser.

So I'm reading this as saying that a DSP cannot have multiple IGs with the same name in different domains, and that a call to update in one top level domain could result in overwriting an IG from another top level domain, although it would retain the bidCounts, joinCounts, and previousWins.

Is this intentional? Based on the overall spirit of the API I would have assumed that these would for sure be partitioned by TLD (FPS but you get the idea)...am I wrong? I have some docs to change if so.