StartWalk in easy. No protocol fog.11 pages
PeopleMeet the builders, creators and scene.25 pages
AppsFind the tools for your digital life.307 pages
NIPsThe rules translated into real moves.267 pages
CraysWhere identity, venues and status get real.17 pages
LibraryEvery chapter, mapped without getting lost.724 pagesNostr Watch gets its own Crays research page because the workbook does not treat it as background noise. It appears in Core and Relays / Infra, usually around Relay directory and Search/discovery, and that means a reader should be able to find it without knowing which directory first mentioned it.
Why this belongs in the atlas
Nostr Watch sits in the relay and infrastructure research layer. The reader question is simple: What does this entry reveal about where Nostr data lives, how it is served, who operates it and what tradeoffs users feel?
The workbook signal says: Relay/network monitoring and NIP-66 tooling. Relay/network monitoring. The Crays version keeps that signal, then turns it into a plain-language map point instead of another cold list entry.
- Route. Relay and infrastructure research
- Workbook area. Core and Relays / Infra
- Subcategory. Relay directory and Search/discovery
- Importance. Core and High
The Crays read
Crays needs this layer because venues, Super Nodes and local rooms cannot be designed from protocol romance alone. Uptime, cost, policy, geography, spam pressure and archive behavior all matter.
The writing rule is the same as the rest of the archive: explain the thing like a sharp friend would explain it over coffee, but keep the facts traceable enough that builders can follow up.
Evidence trail
This derived page is connected to 1 audited source URL(s) and 4 workbook row signal(s). Open the source cards when you want the crawl status, checked subpages and raw research trail.