Spatial Site Genome Strand · genome-spatial-site
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. Define the Kernel (Code), the Cogni (understanding) and the Genome for this." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:471,473]
Content
The spatial_site strand is the extension of the 23-key genome-schema that declares everything the Spatial Site engine needs to instance a venture's spatial journey deterministically. The kernel-spatial-site consumes it as data; cogni-spatial-site governs how its values are chosen; the typed contract is schema-genome-spatial-strand. The worked reference instance is genome-spatial-site.example.json (instance royalorbit-spatial-v2) in this folder.
Strand keys
| Key | Contract |
|---|---|
instance | strand instance id (e.g. royalorbit-spatial-v2); versioned separately from the parent genome |
parent_genome | id of the owning instance genome (e.g. genome-royalorbit) — see genome-schema |
biome | the biome id (e.g. desert-dawn-to-night) plus its theme-arc stops; must match the kernel's THEME_ARC law [src: HOS-Instance/packages/engine/src/engine/contracts.ts:83] |
slices[] | ordered slice list. Each slice: id, story (one storytelling line), ink (dawn/night), scroll_vh (DOM scroll length), holonprints[], budgets |
slices[].holonprints[] | per-holon renderer declaration: method (one of the six holonprint methods; gaussian-splatting implemented), asset (a splat-manifest id — must exist in the manifest, see src-royalorbit), per-tier byte/count budgets (bm-002-splat-budget) |
behavior_loops[] | the life of the sceneries: id, slice, tickHz: 10, seed (deterministic), entities, effects — the BehaviorLoop contract of kernel-spatial-site |
camera_paths | per-slice named paths — at minimum aerial and pov, plus dive transitions, per the aerial↔POV composition rule of cogni-spatial-site |
district_binding | binds the strand to its district: district id (district-spatial-site), squads, pages, and the replication stage |
content_hash | drift detection, same discipline as the parent genome-strand |
Determinism rules
- Every
assetid must resolve in the splat manifest — no unlisted assets (the loader is manifest-driven [src: HOS-Instance/packages/engine/src/engine/contracts.ts:36]). - Every behavior loop carries a fixed
seed; a regenerated instance replays the same life (the 40-regenerations principle of genome-schema). - Per-slice budgets must sum within the kernel ceilings (
SPLAT_BUDGET: 700k desktop / 300k mobile visible splats [src: HOS-Instance/packages/engine/src/engine/contracts.ts:149]). - Slice order defines the scroll journey; transitions are slice-boundary properties, not ad-hoc — "the immersive transition between them" is declared, not improvised [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:471].
- The strand carries the venture's meaning, not just visuals: slices bring "elements of Browser data, User data, and everything related to the venture genome, their endeavors (programs, Products, Profissionalization) and Experience loops" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:465] — see endeavorbook.
Composition
- uses: genome-schema (parent contract), schema-genome-spatial-strand (typed form), biome slice scenery holonprint (declared units), bm-002-splat-budget (budget law), gaussian-splatting + spark-renderer (implemented method)
- used-by: kernel-spatial-site (consumes as data), cogni-spatial-site (decision surface), district-spatial-site (the instanced district), squad-instance (builds against it), bp-001-spatial-site (blueprint), sc-001-kernel-cogni-genome (flow schematic)
See also
- [genome-spatial-site.example.json](genome-spatial-site.example.json) — the real
royalorbit-spatial-v2instance - genome · spatial-site
- pb-001-spatial-site-loop — the loop that augments this strand's particles