The .well-known/ suggestion from neilv is worth taking seriously. It's an IANA-registered convention that already has broad adoption — security.txt, robots.txt equivalents, app associations, and a growing number of machine-readable discovery files use it. Putting the discovery document at /.well-known/satproto.json instead of /satellite/satproto.json would immediately signal to anyone familiar with web standards that this is a protocol endpoint, not a page on your site. It also avoids the path collision problem that the satproto_root.json fallback is trying to solve — .well-known is reserved specifically so it doesn't collide with your content.