Kayla
NewEngine
A shard of something greater.
NewEngine is an early-stage engine technology project focused on explicit boundaries, replaceable providers, and inspectable runtime systems.
It is built around a simple idea: complexity is acceptable when ownership is clear. Hidden runtime behavior, silent fallbacks, and hardcoded asset paths are not.
Core Principles
| Engine as Host | The core coordinates lifecycle, routing, scheduling, and diagnostics. |
| Service as Plugin | Systems are implemented behind declared contracts and can be replaced. |
| Capability as Option | Optional features are visible, testable, and profile-controlled. |
| Data as ListFile | Assets are described through addressable data, not runtime hardcode. |
| Runtime as DTO Pipeline | Providers receive data, return data, and the runtime owns the apply stage. |
Current Direction
NewEngine is moving toward a data-driven asset graph where archetypes, drawables, materials, textures, packages, runtime services, and debug output are all traceable.
The immediate goal is not feature overload. The goal is a stable vertical slice that proves the architecture by running: clean loading, clear ownership, visible diagnostics, and no hidden legacy path.
Status: work in progress.
Host. Plugin. Capability. ListFile. DTO. Diagnostics.