Does my repo need to be public to register?

[amacsmith]

Q: Does my repo need to be public for me to register a knowledge graph here?

A: Yes — the registry only indexes public graphs today.

The registry is pointer-only: every entry's graph_url is fetched anonymously by the nightly sync from raw.githubusercontent.com (or wherever the producer hosts it). There is no auth path, no token storage, no proxy layer. If the URL isn't reachable without credentials, the sync marks the entry missing and eventually dead.

This is intentional. The registry is designed as a public directory of public maps — anyone with the URL can fetch any indexed graph, no SDK, no signup. Adding private-graph support would require either:

• A private aggregator running inside your perimeter that speaks the same shape (CKGP v1 §9 explicitly allows this — the protocol is multi-vendor by design), or
• A central proxy holding tokens for every registered private repo, which we're not going to build.

If you have private code that you want a private agent to understand, the right move today is to run a producer locally (Understand-Anything, GitNexus, etc.) and point your agent at the resulting file directly. The CKGP .well-known/code-graph.json discovery convention works just as well behind a private network — you just don't list it here.

A future "private-publisher tier" — likely a small self-hostable aggregator template — is on the radar but explicitly out of scope for v0.1. Comment on this thread if it's something you'd use.