conceptcanonicalOWNER-2026-07-10

Slice · slice

Owner directive (2026-07-10), canonical. "Start by defining the biom, scenaries (Slices), their components interacting with its elements, the Loop Routine of it and the immersive transition between them." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:471]

Content

A Slice is a scenery segment of a spatial-site: one bounded stretch of the journey, declared with everything it needs to live. Per OWNER-2026-07-10 a Slice is defined by four parts:

  1. Components + elements — its COMPONENTs (React / pods) interacting with its ELEMENTs (data), per the CodeLand ladder [src: wiki/engines/cognis-and-kernels.md:52-55];
  2. Behavior loops — "the Loop Routine of it": loops that give the slice life (routines of beings, physics events, dynamic events) — "sceneries running with Loops of behavior, so it shall literally be a drone flight over a live scenery" [src: ...knowledge-management-and-concept-modeling.md:461];
  3. Transitions — "the immersive transition between them": continuous, story-telling movement into adjacent slices ("continuous transition even over pages. with story telling transition" [src: ...:594]);
  4. The biome laws it inherits — the slice never redefines the environment, it instantiates it.

A Slice lives inside a scenery (the lived spatial environment); operationally it maps to a chapter of the render engine: the proven Royal Orbit build assigns each chapter a disjoint world-space slab, its own splat assets, and camera keys — "Each chapter owns a disjoint slab of world space along -Z so meshes never overlap and can co-exist while adjacent chapters are both resident" [src: HOS-Instance/packages/engine/src/engine/contracts.ts:166-178]. Slice content renders through holonprint loops; slice sequencing is declared in schema-genome-spatial-strand.

Composition

See also

Linked from — 23 cards