Loading
94 technologies joined by 119 recorded dependencies in 6 layers. 31 foundations need nothing else in the corpus; 41 end products are needed by nothing further. Pick a root to see what one technology cannot exist without, and what stops if it fails.
94 technologies, 119 dependencies, 6 layers. Scroll to pan; hover or tap a tile to trace what it needs and what needs it, and open its page from there.
A chokepoint is a step whose removal splits the map: technologies downstream lose their only route to the foundations. These are where a recall, a plant fire or an export control does the most damage.
Steps with exactly one vendor company in the corpus. Some are genuinely sole-source; others just need more companies recorded, so treat this as a list to check rather than a verdict.
The deepest dependency chain in the corpus, foundations first. Every step must hold for the last technology to be delivered.
Technologies with the most direct dependents. Improving one of these lifts everything to its right on the map.
Each technology record can name the technologies it cannot be delivered without (dependsOn in src/data). A node sits one layer to the right of its deepest dependency (longest-path layering), and within a layer nodes are ordered by a few barycentre sweeps so arrows cross as little as possible.
Only true, uncontroversial requirements are recorded: manufacturing steps, instruments, software and upstream methods. “Often used with” is not a dependency; that lives in pairings and related links.
Chokepoints are articulation points of the map that something depends on; the longest chain is the deepest path; single-vendor steps count the companies linked to each technology in the corpus. Each is a prompt to look closer, not a judgement.
Missing a dependency? Add the id to the technology's dependsOn array, run npm run validate, and it appears here and on both technology pages. Every technology page also shows its own “Depends on” and “Needed by” strips. The wider graph explorer shows every other kind of link.