Graph

Five registries, one picture. Every line here comes from a field somebody filled in on purpose, an agent naming the server it can reach, a note naming what it is about, a project naming the stack it runs on. Nothing is inferred from a shared tag, because a tag overlap produces a plausible edge and a wrong one about equally often.

Drawn once at build time, with no client JavaScript at all: hovering or tab-focusing a node dims everything outside its neighbourhood using generated :has() rules. A force layout would have cost an island, moved between builds, and made the picture impossible to describe in words.

Relationship graph: 49 connected entities and 58 relationships between them. The list beneath this graph carries the same information as text.SYSTEMS · 8MCP · 2AGENTS · 7PROJECTS · 20NOTES · 12Proxmox node, system, runningMedia pool, system, runningHouse network, system, runningGitHub, system, runningNotion + Super.so, system, runningVercel, system, runningSupabase, system, runningApple platforms, system, runningzckr-lab, mcp, onlineLinear, mcp, onlinedoubt, agent, activescout, agent, activeclaims-auditor, agent, activeship-captain, agent, activeplanner, agent, activeremediator, agent, activeperf-sentinel, agent, activeBrink, project, buildingfelt., project, buildingPuttX, project, shippedZoomies, project, shippedLossless Library, project, buildingProxmox Server, project, shippedHouse Network, project, shippedAgent Harness, project, buildingBrand Assets, project, pausedacker.cloud, project, shippedzckr.dev, project, buildingKirsten Blair Co, project, pausedOpen-Weight Models, project, experimentthrivecmd.com, project, shippedStagger, project, shippedaeroslip., project, buildingcollect., project, shippedSwing Sight, project, deadtwoThings, project, shippedPictr, project, shippedThe Machine Plays First, note, noteEighteen months of bad RAM, and the mail server that hid it, note, noteThe auditor should not hold the pen, note, noteThe bug class that compiles: work built on a premise that moved, note, noteAn interactive dependency graph with no JavaScript, via :has(), note, tilBuilding zckr.dev: content as data, everything else follows, note, noteOut of the box, an MCP server answers curl with a 406, note, notePlaywright's --update-snapshots silently skips files inside the tolerance, note, tilpnpm 10 blocks dependency postinstall scripts by default, note, tilTailwind v4 keyframes live inside @theme, note, tilThree numbers that changed a design, note, noteBuilding Pictr: a photo app that cannot phone home, note, note

49 connected · 58 relationships · hover or tab a node to isolate what it touches

Legend

runs-on
“runs on”
serves
“serves”
uses
“uses”
belongs-to
“belongs to”
documents
“documents”

Every connection58

The graph above, written out. Ordered by how connected each thing is.

Standing alone6

These are not drawn above, because a box with no line to it reads as a rendering bug rather than as information. They are named here instead of quietly dropped: most of them are single-file things with no dependency worth recording, which is a fact about the projects and not a gap in the data.