"Where this collection belongs to" is not much important in atproto. Because there is only one content owner: atproto identity. Regardless of you are human or a labeller, you share same collection NSIDs. Even if we do split git repository identities from user accounts, it's not that hard to imagine `org.tangled.feed.{comment,reaction}` or `org.tangled.key.sshKey` being owned by a git repository. A git repository will probably never own `org.tangled.feed.star` but we don't say it's `org.tangled.user.feed.star`. Git repository is a valid atproto identity. It can technically own anything. If we don't do stuffs like below, omitting "repo" as a feature scope should be fine. - `org.tangled.repo.ci.*` - `org.tangled.repo.git.*` - `org.tangled.repo.label.*` - `org.tangled.repo.secret.*` - `org.tangled.repo.webhook.*` "A git repository" is too broad topic in Tangled that having `repo.*` group to scope feature doesn't do much job. Signed-off-by: Seongmin Lee <git@boltless.me>