concinnity-core: the engine's RUNTIME vocabulary and the CPU compute over it.
The types the renderer, the cook pipeline, the subsystem crates, and the
editor all have to agree on and none of them owns: the backend-agnostic GPU
data layouts the CPU and the shaders both name, the transform and skeleton
math those layouts are expressed in, the ECS storage mechanism plus the
component definitions and the registry built from them, the post-process /
quality setting structs, the behavior virtual machine that evaluates
declarative logic, and the .cnb blob container format the cooked world
travels in.
Above that vocabulary, the kernels that compute over it and belong to no
single consumer: skinning and pose blending, IK, LOD decimation,
rasterisation, IBL convolution, the procedural geometry generators, and the
payload codecs (build, decode). Each asset's AUTHORED schema (what a
world.jsonl declares) sits in components beside the runtime half it bakes
into; the build-only assets, which never reach a running world, live with
their registry group in concinnity-world. The asset COMPILE pipeline is
concinnity-cook, which this crate has no edge into.