Access around Mjolnir owners doesn't match up with communities.

Nobody has claimed this yet.

Access to a particular mjolnir (whether that mjolnir is still run) is managed by the owner.
If we remove an owner's access to a mjolnir, we also end up closing out anyone else in that mjolnir's management room from using the mjolnir.

>What I mean is that we can have the following:

>1.User A is in good standing.
>2. User A creates a Mjölnir.
>3. User A steps down, letting user B be the de facto owner of this Mjölnir.
>4. User A becomes an obnoxious troll and gets kicked out from the server.
>5. We remove A's authorization to generate Mjölniren (I think I'm going to keep that plural :) ).
>6. Any Mjölnir of A gets closed.
>7. B loses a Mjölnir.
>The only reason I can think of for indexing Mjölniren by creator is to do 6, no?

No files, tests, or entry points are named. Start by tracing how Mjölnir ownership, authorization removal, and management-room membership are represented, then inspect where creator-based indexing triggers closure. Done should preserve access for remaining managers while retaining the intended behavior for Mjölnir instances whose authorized owner is removed.

Written by the indexing model from the issue text.