developer/map PUBLIC DATA / NO SIGN-IN

>_ DEVELOPER KNOWLEDGE / SOURCE EXPLORER

Trace a relationship.
Check its source.

Explore connections between networks, languages and infrastructure. Select a link to read its source record; editorial additions are labeled.

DOCKER CONNECTIONSDOCKER

Three examples. Select one to inspect its source.

Docker connected concepts

Loading graph relationships…
Loading source recordsCLICK TO INSPECT ↗
—canonical records
—explicit relationships
—cross-source concepts
Source records preserved. Editorial connections labeled.

01 / WORKSPACE

Explore the connections.

Select a node to see its connections, or use search and the source index without the canvas.

01 — 03
developer.graph{ } sources.json↳ learning.pathsKNOWLEDGE GRAPH
WHOLE FIELD / ALL NODES
CLICK A NODE TO SEE ITS LINKS · DRAG · SCROLL TO ZOOM
LINE STYLES
$ inspect Select a concept to reveal its connections.

02 / SOURCE LEARNING PATHS

Trace a learning path.

Follow a source’s suggested sequence, then inspect each concept and its connections.

02 — 03

03 / ORIGINAL MATERIAL

Open the source.

Browse every imported record, including claim and reference nodes. Open a record to inspect its fields, evidence, and original JSON.

03 — 03
{ }

TRACE THE SOURCE

Download the original records.

Original JSON files are available below. Reviewed aliases share one concept; distinct meanings, claims and references stay separate. Editorial links include a rationale.

An arrow records the direction of the source link; it does not by itself prove causation or an operational prerequisite.