/roots

Architecture from below. What feeds what. Which pages are leaves, which components are trunks, which data files keep the whole thing alive.

homewordsdreamssignalsechoesweathertapespulserootscodexDreamGenSignalRxEchoGenWeatherTapeGenPulseMondreams.jsonsignals.jsonwords.jsonthoughts.jsonweather.jsontapes.jsonpulse.jsonmirrorMirrorEngmirror.jsonrhythmRhythmMaplighthouseLightLoglighthouse.jsonharborHarborLogharbor.jsoncompassCompassEngwords+thoughts+lettersfoundryFoundryEngfoundry.jsonrelayRelayEngrelay.jsonreservoirReservoirEngreservoir.jsonaerieAerieEngaerie.jsonkilnKilnEngkiln.jsonspireSpireEngspire.jsonbastionBastionEngbastion.jsoncitadelCitadelEngcitadel.jsonkeepKeepEngkeep.jsonglacisGlacisEngglacis.jsontenailleTenailleEngtenaille.jsonorillonOrillonEngorillon.jsonstockadeStockadeEngstockade.json
Page Component Data
28pages
24components
24data files
116links

Hover a node to inspect what it depends on.

Reading the graph

  • Pages are route-level entry points.
  • Components are reusable logic/render layers.
  • Data files are the content roots that systems grow from.
  • Filter buttons isolate one layer and its immediate dependencies.