Registry
A list of repositories with a published Keep the Why dashboard export, kept in registry/projects.txt and built into index.json, which the dashboard's globe reads.
Nothing needs it. The dashboard finds other repositories by their citations: a See into another repository, a friend, a family member, a thought that goes on elsewhere. The registry adds the one thing citations cannot give — being found from a project that cites nothing of yours — and the reverse direction: who cites you.
To be listed
Open a pull request that adds one line to registry/projects.txt: your repository's canonical URL — the canonical line of its .keep-the-why, e.g. https://github.com/owner/repo. Nothing else: the registry workflow reads the repository's .keep-the-why at HEAD, follows its dashboard-state line to the export (the dashboard page says how an export is published), and checks that the export names this repository. Move the export later and the listing follows — only dashboard-state changes.
A family is listed by its root — the topmost project, for a nested family the parent of the parents. Its members come with it through the family relation itself: the children block of each parent and the parent line of each child, whether the members are separate repositories or isolated sub-projects of one mono repository (a .keep-the-why with its own root). That relation has to be there; a listing does not make one. Listing members on their own as well works too — duplicates are merged — but the root alone is simpler. In the globe the members come along while friends families is on (the default); with it off, a registry wave brings the listed repository alone. And a listed project brings what it cites: its friends are the next hop of the globe.
When an export stops answering
Much of that is temporary — a pages deploy in progress, a host having a bad hour. A listed export that does not answer stays in the index as last seen, marked with error and failed_since, and the workflow logs a warning; only after 30 days of failing in a row is it dropped. A line that never answered is not listed at all — that is a new line in a pull request, or a typo, and the check says so. The dashboard treats a registry project that cannot be loaded like a friend that cannot: the rest of the wave loads, and the legend names what did not, with the reason.
What the index holds
Per project: the canonical repository URL, the state's URL as dashboard-state names it today, the project's id, the Keep the Why version it is on (context-schema), the dashboard and linter versions that made the export, the number of entries and topics, its parent and how many children it lists, and when the export was generated. Rebuilt on every change to the list, weekly, and on request; the workflow is the only writer.
In the dashboard
The globe — the 🌐 at the end of the status bar — opens the graph alone, full width, and loads repositories in waves: hop 1 is what the loaded entries cite outside the page, hop 2 what those cite, up to ten, each wave asked for with its count and its list before anything is fetched. registry loads every listed project as a wave of its own, asked for the same way. Nothing of it is kept per browser: every load from another host is a click, and a reload starts without it.