Wax Trax posted it as a meme.
I made the first iteration. If you know how GitHub works, and have something to contribute, let me know.
This project began by reverse-engineering and expanding the relationship web in the image above. View the original post on Facebook.
This repository is ready for GitHub Codespaces. Open the repository in a Codespace, then run:
npm run devCodespaces automatically forwards the preview on port 4173. Run npm run build to create a production build in dist/.
The first working explorer is a static Vite application. Its portable graph lives in data/industrial-graph.json and is bundled at build time; no database, server, or hosted application is required. Run npm run validate before changing graph data, then npm run dev to explore it locally.
The graph is evidence-backed rather than dependent on a single database. MusicBrainz provides structured credits, while Wikidata provides independently maintained cross-references and exact mapped relationship claims. Official artist, label, and release pages may also be cited. Discogs links are retained as catalog cross-references; its API content is not bulk-imported without the required attribution and credentials.
See docs/knowledge-model.md for the canonical node, relationship, provenance, and temporal conventions.
See docs/scoring-model.md for how documented industrial contribution and the composite graph score are calculated.
See docs/chatgpt-setup.md for the optional ChatGPT companion workflow and a workspace-eligible custom GPT configuration.
Merges to main build and deploy the site through GitHub Pages. In the repository settings, set Pages → Build and deployment → Source to GitHub Actions once. The public site will then be available at https://dphunct.github.io/Knowledge-Graph-of-Industrial-Music/.