Skip to content

Slang lineage map

Interactive 8 families · registry + YTD leaves Static export · not live DB Similarity / map ≠ Brier

One glance: hubs are families, size is term count, color is domain. Click a hub to open leaves. Search jumps to the family that owns a term.

How to read

Map position and cosine neighbors are structure, not forecast skill.

Reading evidence →

Docs

Mutation operators, family write-ups, Mermaid sources.

Slang lineages →

Instant legend

You see Means
Center hub All families (click to reset)
Ring of disks One lineage family each
Disk size Number of atomic terms in registry
Disk color Domain hue (betting, crypto, AI, …)
Orbit labels Atomic terms after you open a family
Dashed arc Within-family hash-embed neighbor (INFERRED · not Brier)
Month chip First seen in YTD backfill packs (if any)
URL Opens
?term=rizz Family + selected term + neighbor arcs
?family=brainrot-aura Family expanded
?family=ai-native AI-native hub
?q=steam Search filter

Use Copy link on the map toolbar after selecting a term.
From a pipeline receipt with lineage, open:

…/map/?term=<primary_term>
# or
…/map/?family=<family_id>

Why this shape

Slang is not a flat dictionary. Hyperlex stores phylogenetic families (root payload → trunk → branches → leaves). A radial constellation keeps:

  1. Global structure always visible (8 hubs)
  2. Local detail on demand (terms after click)
  3. No force-layout spaghetti on first paint

Static Mermaid family trees still live under examples/slang-families/. This map is the overview instrument for researchers and operators.

Data source

Field Source
Families + terms LINEAGE_REGISTRY in hyperlex.analysis
First-seen months data/backfill/2026/*.json
Export scripts/export_lineage_map.py → map/lineage-map.json 
python3 scripts/export_lineage_map.py
# commits docs/map/lineage-map.json for Pages

Machine graph: lineage-map.json