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.
Thin frontend, one wire-mapping seam
• Cropwright only displays/sorts — the backend owns decisions and serves them as data
• api.ts is the sole place RawCrop/RawCluster get mapped into the app's types; nothing else parses the wire shape
Controllers own action logic, pages own state
• A page keeps queue/cursor/handledIds; a controller (factory function, closures over passed-in accessors) does assign/discard/skip/undo against that shared state
• Same convention for /clusters/[id]'s clusterController and /clusters' slotGalleryController
Region features gate on one served value
• region_profile: null on GET {prefix}/health means zero region routes are called — no region tab, no gallery, no keymap letters
• A tier-2 slot that touches a region route is kept only when its key matches the served profile's name