The engineering
Why not just use Unity?
The original answer was that the engine work was part of the project: explicit control over rendering, platform targets, asset formats, update order, and diagnostics. The more important answer came later. Once Dungeon Dice needed the reusable parts, keeping the engine and generator conceptually owned by the cat game stopped being a useful boundary.
The boundary became real
Chaos System now owns the reusable layer: entity/component runtime, scenes, transforms, rendering, GPU resources, input, physics, animation, audio, UI, windowing, platform seams, and deterministic generation. Purrfect Chaos owns the cat, the island, the quests, the economy, the ecology, and the composition that turns those mechanisms into a game.
The split is an architectural outcome worth preserving: Purrfect is the birthplace and a consumer, not the owner of a shared engine stack. A second game is what makes the distinction testable.
The world is a place, not a backdrop
The island layer uses a Moreton Island-derived heightfield, named locations, terrain zones, ecology, and species rather than a generic superellipse with scattered props. This introduces a deliberate scale boundary: terrain geography and landmark spacing use the world scale, while characters and props use their own readable mesh scale. Mixing those units makes placement wrong even when the arithmetic looks plausible.
The renderer is a system, not a screenshot
The rendering path spans backend-neutral engine contracts, native graphics backends, shaders, materials, batching, cameras, terrain, generated assets, and diagnostics. Dedicated validation, profiling, reproduction, performance, and terrain tools exist because a renderer that fails only on one driver is still broken. Native backend implementation, automated tests, and observed pixels remain separate evidence levels.
Motion and sound have the same problem
Player locomotion now has articulated legs, IK, body weight, and steering work instead of treating the cat as one rigid moving mesh. Music has more instrumentation, longer form, deterministic variation, and real transitions. These changes exercise the game/engine seam while leaving the meaning of the cat and its world in the game layer.
Data flow and determinism
Purrfect-owned catalogues and game state flow through Chaos-owned runtime structures. Deterministic seeds and validation harnesses make generated scenes reproducible enough to debug, while the consumer still decides which generated assets appear and where. The generator is a production tool, not a hidden second game.
The honest cost
Owning less of the shared layer does not make the game simpler. It makes the responsibility legible. The alpha still carries platform, shader, asset, and content costs, but improvements to genuinely reusable capability can now serve another consumer without importing cat-specific assumptions into the runtime.