The machine
The structure is the dependency graph
Each gear is one built @platform-modules/* package. A gear’s size tracks how many other modules depend on it — the foundation everything rests on turns the largest. Two gears physically mesh when one actually imports the other, at an exact tooth ratio, so the drive propagates exactly the way dependencies do. Modules that depend on nothing are independent driver gears; modules with more than one dependency mesh their primary one and link the rest with glowing rods.
Sized by dependents
db and util are imported by the most modules, so they’re the big drivers. Leaves that nothing depends on are the small gears.
Meshed by import
Where one module imports another, the gears interlock and counter-rotate at the real tooth ratio. No mesh means no dependency.
Rods for the rest
A module can depend on several. The primary dependency is the mesh; each additional one is a lit linkage rod between hubs.
Click for the data
Every gear is labelled. Click it — or a card below — to open its full record: layer, status, dependencies, dependents, capabilities and providers.
The catalogue
Twenty-one gears, à la carte
Every built @platform-modules/* package. Click for the full record, or spotlight its gear in the machine above.
Tip: a card opens the module’s data and flies the camera to its gear.