Who owns each system, what depends on what, and what's at risk across Lawhive's product estate.
Ownership and health are auto-discovered from git; humans confirm them via PRs to
registry/.
loading catalog…
Couldn't load catalog.json. Serve this over HTTP (not file://) and re-run scripts/build.py.
What needs attention
–single-owner systems
Ownership confirmed
0/ 0
clear
System
Domain
Owner
Lifecycle
Live (prod)
Bus factor
Last commit
Comps
Flags
Rows highlighted in red are single-owner (bus factor ≤ 1) and not external. Live (prod) = has a deployed Tofu stack (lhctl sr); blank = no Tofu stack (e.g. Vercel apps, libraries). Bus factor = fewest contributors covering ~80% of commits. Component counts exclude Terraform deployment wrappers. Click any row for detail.
activemaintenancedeprecatedexternalnode size ∝ components · green ring = confirmed owner · dashed box = domain · arrow = depends-on · click a node for detail