Start here
Click a cluster
Each cluster on the diagram is a group of files that do one job together. Click any of them to see what it does, the files in it, and how it connects. Then click a file to see its annotated code.
How to read the map
The writer-facing flow is left-to-right after the shared recipe layer: definitions (1) and runtime (2) describe the composition language; the editor planner (10) interprets recipes into authoring plans; the editor UI (3), admission/insertion registry (4), and document workspace (5) turn that language into Write mode; persistence (6), public rendering (7), extraction/import (8), and tests (9) consume the same saved ContentNode contract.
The big idea
The editor UI does not own a separate composition model. It is an authoring interpretation of the same recipes and nested slots.* JSON that preview, public rendering, extraction, and tests consume. Frame paints the page canvas; normal recipe-backed compositions render reusable content inside it.
Tip — once you select a cluster, you can click any file in it to drill in.