Why build an AI-native engine
Most game-engine APIs are written for humans. When AI becomes the one writing the code, the engine should look different.
ForgeaX's core idea is simple: the user describes a game, and AI writes the engine code. That sounds like "just a different author," but in practice existing engines aren't friendly to AI — they assume a reader who reads docs, guesses, and fills in context like a human does.
Our stance is blunt: AI is the engine's first user. When "friendly to AI" conflicts with "friendly to humans," AI wins. Here are a few concrete consequences.
1 · One source of truth, derive the rest
A fact is defined in exactly one place; everything else derives from it. Component fields, for instance, live inline in a schema — inspectors, debuggers and tooling read the schema instead of grepping source and guessing. AI doesn't need to "remember" conventions scattered everywhere, because there's only one place to look.
2 · Errors AI can understand and recover from
An error isn't just a human sentence you throw. We use a closed set of error codes, each carrying structured "what / why / how to recover" info. When AI hits an error, it knows what to change next — instead of treating the exception text as mysticism.
3 · Structured data instead of "look at the screen"
The hardest part of a rendering bug is that "it looks wrong on screen." A human can stare at the monitor; AI can't. So the engine can capture a frame of render calls — draw calls, bindings, render targets, pipeline state — to read offline, replay, and inspect the full state at the Nth draw. A visual problem becomes data AI can Read.
4 · Two implementations that check each other
The render layer has two backend implementations (WebGPU and a wasm one) behind a single interface. They render side by side: the moment AI misuses an engine API, the other backend immediately diverges, surfacing the problem — far faster than waiting for a human review.
These designs share one yardstick: the fewer concepts a reader (human or AI) must hold in their head, the better. The more self-consistent and locally-indexable the API, the more often AI gets it right — and the easier it is for a human to take over.
"AI-native" isn't a slogan — it's a long series of "redo it for the AI's point of view" decisions. We'll unpack more of them in the docs and future posts.