Defining which snaps are maintained by Canonical and what that really means seems like a topic we can cover in the next product sprint in July.
We can already try to define a base line, though. At a bare minimum, it sounds like such snaps need to be maintained by a well defined group of people, with a clear plan including security updates, and under known terms which include what level of support is offered and for how long. Without any of those we can't really claim the snap is supported.
If we have that for a snap then it seems fine and somewhat expected that it'll be published under the organization account, and ideally we should make those terms and processes more clear. If we don't, then it feels more like a personal initiative without a stronger commitment from the organization, and might be published under the personal account, at least for the time being.