Compiled, without an interpreter
The implementation documents an ahead-of-time path from Kalcite syntax to HIR, MIR, a Rust backend and platform-specific output. A deployed program does not embed a Kalcite bytecode VM.
Predictable game memory
Fixed pools and generational handles are part of the language model. They provide a bounded home for game objects while making stale references detectable.
A real project format
Projects use kalcite.toml, scripts, scenes, assets and input maps. The CLI can
discover and validate a multi-script project before building it.
Native targets with measurable constraints
Kalcite validates a constrained-hardware reference implementation, a desktop development route, and a TI build route. NumWorks provides the current EADK integration; WebAssembly remains planned.
Scenes for application UI
Static GUI controls, containers, focus and signals are already part of the scene pipeline. The roadmap extends them toward native application UI with explicit profiles and capabilities, adaptive layout, text, bindings and accessibility. Those richer features are planned or in progress, not presented as current runtime behavior.