The machine
The structure is the dependency graph
The main deck contains every @platform-modules/* package. Templates, plugins, presets, blueprints, delivery stages and roadmap parts occupy their own mechanical rails around it. Drive rods show declared dependencies and bundle relationships; choosing a blueprint assembles only the parts needed to build that product.
Main drive deck
All shipped, designed and roadmap modules are present. Framework siblings and UI packages remain distinct gears rather than disappearing into their core package.
Upper assembly rails
Templates and plugins sit above the package deck and connect to the modules they consume, bundle or require.
Product flywheels
Presets feed blueprint flywheels. Selecting a blueprint isolates its complete dependency closure, including templates and plugin-provided modules.
Click for the data
Every mechanical object has a catalogue record. Click a part to inspect its kind, status, relationships, 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.