Spatial Site Cogni · cogni-spatial-site

Owner directive (2026-07-10), canonical. "The District Spatial Site (brings the environments create by the datans with DROIDS living in the CodeLands and their hibrid existence in the world, places, products, assets, pricess, experiences, collors, smells, these are all constructed by datans, to build each venture fully as a Universe of Ventures, Endeavors, Goods, Individuals, Organizations, SQuads, Droids, Dynamic Events, Dynamic Runs, Full Augmentation." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:520]

Content

A cogni is an engine's understanding — the instructions a datan or looper loads before touching the kernel [src: wiki/engines/cognis-and-kernels.md:3]. This Cogni states what the Spatial Site district IS and the decision rules for composing it. It never contains code; the code contract is kernel-spatial-site.

What the district IS

The Spatial Site is a venture's welcoming spatial environment — a guided, living, scroll-driven journey through the venture's universe, "a spatial digital place of experiencing the oganization of the likemind drive in a a joint endeavor" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:504]. It renders the venture genome — its endeavorbook dimensions (programs, products, professionalization) and its venturebook divisions — as sceneries with life. Ventures manifest it as remote-islands: "Ventures have remote islands which operates like skyboxes, vexxel expansive survival-driven, prosperity inspired creation of spaces" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:522]. The bar is explicit: "It should fell like mont-fort.com, it should impress like genie3" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:582].

Decision rule 1 — which holonprint method to pick

Rule: never block a slice on an unimplemented method — compose with gaussian-splatting now, register the intended method in the genome strand, and let a future run on that holon upgrade it [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:496].

Decision rule 2 — how slices map to sceneries

A slice is a chapter of the journey (a Chapter in the kernel); a scenery is the living environment inside it. Composition order per slice, owner-fixed: "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]. So: biome first, then slices, then components↔elements, then the BehaviorLoop routine, then transitions. Every slice must declare its assets, camera keys, and behavior loops in genome-spatial-site before any build particle is dispatched.

Decision rule 3 — the read-order

A Datan composing spatial work reads in this exact order and may not skip a step:

1. Cogni (this card) — what and why;
2. kernel-spatial-site — the code contracts it must satisfy;
3. genome-spatial-site — the instance parameters (which slices, which seeds, which budgets);
4. pb-001-spatial-site-loop — the playbook of concatenated cookbooks (cb-spark, cb-threejs, cb-lenis, cb-gsap, cb-react, cb-tailwind) for the loop itself.

This is the local application of the library law: "dont let the Neural Engine Execution or the Neural Ware Agenticly gettings things done stray a single word from the Kernels and the knowledge in general at the Library" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:610].

Decision rule 4 — the dawn→night emotional arc grammar

The journey's emotion is carried by the biome color law, implemented as THEME_ARC (dawn ivory #F5EFE0 → golden hour → dusk amber→umber → night gold #080600) [src: HOS-Instance/packages/engine/src/engine/contracts.ts:83]. Grammar: dawn = welcome and identity; golden hour = the work and the divisions; dusk = weight and mastery; night = scale, legacy and the stars. For Royal Orbit the plot mood is owner-set: "Go with old arabic letters forming the scenarios, sand and muslin brotherhood, world, security tradition and vision for emotion of the plot" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:482]. A slice's ink and fog must come from the arc — never ad-hoc colors.

Decision rule 5 — aerial ↔ POV composition language

"use aerial and pov view even when the scenarios are literally right neext to the other, so you have the presentation and transition of space as sistemic view and immersion as personal experience" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:524]. Therefore every slice declares at least two camera paths in the genome — an aerial (systemic presentation) and a pov (personal immersion) — and transitions between slices alternate the register: arrive aerial, descend (dive) to POV, depart aerial. The physics of the flight obey the environment's laws (space, air, dive, distancing, gravity, action/reaction) [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:500].

Composition

• uses: kernel-spatial-site (contracts), genome-spatial-site (parameters), biome slice scenery holonprint (units), pb-001-spatial-site-loop (loop playbook), bm-002-splat-budget (budget law), remote-island (venture manifestation)
• used-by: district-spatial-site (the district this Cogni governs), squad-instance + squad-eggtech (squads that must load it before looping), cogni-neural-engine (fans out particles against these rules), bp-001-spatial-site (blueprint)

See also

• sc-001-kernel-cogni-genome — how Kernel, Cogni and Genome interact and flow
• cognitive-loop — the rule this Cogni is a stage of
• src-royalorbit — the live v1 the grammar was extracted from