Module app 

Client application runtime: the world loop and the runtime systems that drive a compiled world. The build / edit / debug / preview paths live in the editor crate. pub so the editor crate (which drives a live App via the runtime API) can reach these runtime app items through concinnity_engine::app::*.

Re-exports

pub use run::run;

Modules

anim_runtime

Process-wide command queue for runtime animation control (crossfades, graph parameter writes, graph state queries). Mirrors the shape of crate::debug::runtime_spawn, but separate so the AnimationSystem can drain its own commands without contending with GraphicsSystem’s decal / particle queue.

budget

Process-level thread + memory budgets computed at App start.

dev_flags

Process-wide flags shared between the engine loop (library) and the binary-only cn debug subsystem. Only the flags the library itself names live here; the world.jsonl / shader-stage “changed” flags and the decal / emitter spawn queue moved fully into the binary-only debug tree (crate::debug), since nothing in the library references them.

mem_drift

Long-session drift of process memory against the tracked heap.

run

The runtime player path. Loads compiled blob data and drives the system loop. Fully synchronous – no Tokio runtime here. Systems that need async (HttpServerSystem, LlmSystem, etc.) spin up their own runtimes internally.

runloop

The shared render/event loop that drives a live App. Both the compiled cn run runtime (run::start_runtime) and the interpreted cn debug path (in the editor crate) pump the same loop; the only difference is the per-tick hook the debug path threads through to run its DebugHook. Keeping the platform event-pump and window-activation glue in one place means it is not duplicated per entry point.

startup_error

Classification of fatal startup failures into a log line plus a sentence for the error screen.

state

The App value a host constructs, starts, and steps. The App value: a world plus the loop state that drives it.

syscpu

Host-memory queries backing the memory budget + the live-usage readout.

sysmem

Host-memory queries used to compute the process memory budget (see app::budget) and to report live usage. Two values, each best-effort: the machine’s total physical RAM (the budget is a fraction of it) and this process’s resident set size (what it is actually using now).