Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Semantic radar needs more MAP space.
Context
• Before: 67 git repositories in one workspace — a kernel, a module catalog, a design system, a dozen pk-* libraries, client overlays, infra — and 2,122 packages linked into the one binary
• A contract change was a commit in four repositories in a fixed order; almost every repository had one consumer and none was released on its own cadence
Consequences
• One go.mod, one Makefile, one CI workflow, one version; a contract change is one commit and one compile error set
• No boundary is enforced by version string, so the ones that remain (contracts/, internal/) are the compiler's; a single library cannot be released alone, and no consumer wanted it
Evidence
• make check-packages: scripts/check_packages.sh counts go list -deps ./apps/platformkit against the ceiling in packages-budget.json
• check-packages is a prerequisite of make check, which ci.yml runs on a pull request and release.yml runs on the tag; the ADR names no test