Each entry is the question that document answers. If your question is not one of these, the answer
is in the code, and CLAUDE.md's closing table says where to start looking.
- How does a call cross the C ABI, and how does a failure come back?
- How does an asset path become a GPU resource, and what is shared between requests?
- How does a Project file reach the value a plugin reads, and how does a change reach it?
- What does the ECS contract promise about threads and structural change, and how does the flecs plugin keep it?
- What is the framework made of, and what does each piece depend on?
- What does the GPU device contract promise, and what does the WebGPU backend do with it?
- How does a key press reach a system body, and when is its edge visible?
- How does kabic turn a C header into C#, Zig and C, and what stops it going wrong?
- How is the engine divided into layers, and where does each kind of file live?
- How do lights, shadows and image-based light reach a shading pass?
- How does a log event reach a sink?
- How does the managed layer meet the native one?
- How does an authored material become something a pass can draw?
- What does the engine derive from a node type's declaration?
- How do Body2D and Collider2D become a simulation, and what does each tick copy between them?
- What happens when a pass asks for a pipeline that has not been compiled yet?
- How does a frame get from the ECS to the GPU?
- How does one runtime tick run, and what may run at the same time?
- Which threads exist, what runs on them, and how does work reach them?
- How does the engine build view and projection matrices for the device's clip space?