See how your C#, the Unity package source, the compiled engine, and the shared graph canvas fit together.
UnderstandUpdated
On this page
Your PlayerController.cs sits at the top because it is the thing that owns the game’s behavior. Round Trip reads and shows it, then writes narrow changes back to it when you press Compile.
Your C# stays above the Unity integration, while Core and Engine provide the model, parser, layout, persistence, and source-writing work underneath.
The middle layer is the Unity package source: the Explorer, UI Toolkit controls, indexing, settings, menus, and host adapters under Editor/ and Runtime/. You can read and extend that integration.
Under it sit RoundTrip.Core.dll and RoundTrip.Engine.dll plus their dependencies. Core carries the domain model. Engine carries parsing, layout, JSON persistence, authoring, and source writers without Unity types crossing into those layers.
Beside the Unity integration is the io.bitquirky.graph package, which supplies the shared graph canvas and, on Unity 2022.3, loads the package’s SVG icons from their source. com.unity.vectorgraphics supplies vector rendering support.