Phase 15 — the relational moat
The Hardware Graph
Components don't live in isolation. Every part is connected to what it fits, what replaces it, what upgrades it, and what people actually built with it. This graph stores those relations — and it gets smarter with every real build.
Choose a workload to see the best-known components for it.
Path between two parts
e.g. from a CPU to a case — how are they connected through compatible parts?
Why this is the moat
The derived skeleton is knowledge the kernel computes from real specs: which parts physically fit, which are interchangeable substitutes, which are drop-in upgrades, and which serve a workload.
The community layer is what makes it uncopyable. Every published build adds 'built-together' edges and workload associations — the graph literally learns from what people build.