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: 36 connected entities and 40 relationships between them. The list beneath this graph carries the same information as text.SYSTEMS · 6MCP · 2AGENTS · 7PROJECTS · 13NOTES · 8Supabase — system, runningVercel — system, runningGitHub — system, runningNotion + Super.so — system, runningApple platforms — system, runningProxmox Cluster — system, runningzckr-lab — mcp, onlineLinear — mcp, onlineclaims-auditor — agent, activeship-captain — agent, activeperf-sentinel — agent, activedoubt — agent, activescout — agent, activeplanner — agent, activeremediator — agent, activeStagger — project, shippedthrivecmd.com — project, shippedAI Gateway probe — project, buildingKirsten Blair Co — project, pausedzckr.dev — project, buildingacker.cloud — project, shippedBrand Assets — project, experimentaeroslip. — project, buildingcollect. — project, shippedSwing Sight — project, deadtwoThings — project, shippedAgent Harness — project, buildingProxmox Server — project, shippedAn interactive dependency graph with no JavaScript, via :has() — note, tilBuilding zckr.dev: content as data, everything else follows — 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, noteThe auditor should not hold the pen — note, noteThe bug class that compiles: work built on a premise that moved — note, note

36 connected · 40 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 CONNECTION · 40

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

STANDING ALONE · 9

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.