Media, interaction, and product tools
These systems turn engine state into human-visible or editable output. Native
capabilities own devices and low-level resources; aether-kit actors compose
them into reusable camera and mesh behavior.
| Concern | Chapter |
|---|---|
| GPU queues, textures, camera matrices | Rendering and camera |
| Font atlas, layout, text draw | Text |
| Geometry DSL and tessellation | Mesh authoring |
| Realtime synthesis/samples/tracks | Audio |
| Keyboard, pointer, text and IME streams | Input |
| Window lifecycle, mode/title, menu and cursor chrome | Window |
Keep frame ownership explicit. Product actors may emit render and audio mail, but native callbacks and presentation remain chassis responsibilities. For visual changes, pair structural/SubstrateHarness checks with captured evidence; for realtime audio, keep allocation and blocking work off the callback.