StartWalk in easy. No protocol fog.11 pages
PeopleMeet the builders, creators and scene.25 pages
RelaysSee where the network actually lives.50 pages
NIPsThe rules translated into real moves.267 pages
CraysWhere identity, venues and status get real.17 pagesPrimal Article Editor / Reads authoring gets its own Crays research page because the workbook does not treat it as background noise. It appears in Clients & Apps, usually around Publishing, and that means a reader should be able to find it without knowing which directory first mentioned it.
Why this belongs in the atlas
Primal Article Editor / Reads authoring sits in the app and product research layer. The reader question is simple: What does this product surface teach about identity, publishing, discovery, signing, wallets, media or social behavior?
The workbook signal says: Article editor; observed as JavaScript app surface. The Crays version keeps that signal, then turns it into a plain-language map point instead of another cold list entry.
- Route. App and product research
- Workbook area. Clients & Apps
- Subcategory. Publishing
- Importance. High
The Crays read
Crays should read this as product evidence. The useful move is not copying the app; it is understanding which interaction pattern could make profiles, creator commerce, fan access, venue context or payments feel natural.
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 2 workbook row signal(s). Open the source cards when you want the crawl status, checked subpages and raw research trail.