schematiccanonicalOWNER-2026-07-10D8D12

SC-001 — Kernel ↔ Cogni ↔ Genome Triad · sc-001-kernel-cogni-genome

Owner directive (2026-07-10), canonical. "Define the Kernel (Code), the Cogni (understanding) and the Genome for this. … prepare the kernel of CodeLand District Spatial Site, and Atomic Holons for the composition of the data, dynamic work for the dynamic system of interaction." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:473]

Content

The triad every HOS surface is built from — genome (WHAT the venture is, in data), kernel (the CODE contracts it runs on), cogni (the UNDERSTANDING/rules the engines apply). The triad is traversed inside the one rule of the system: "A Loop is valid only once it has run the fixed sequence Cognis → Kernels → Neuralwares. The Neural Engine runs this sequence on every loop." [src: wiki/engines/cognitive-loop.md:3]. Each Cogni "runs on its own kernel (its env, keys, access, data)" [src: wiki/engines/cognitive-loop.md:10]; equipped neuralwares are injected as extra steps [src: wiki/engines/cognitive-loop.md:64].

Naming authority: Genome (not DNA) per D8 — "Rename lib/dna/ → lib/genome/. … GenomeStrand becomes the canonical type" [src: HOS-Webdoc/web/src/data/hos-specification.ts:557]; the Neural Engine that runs the traversal is the 5th, kernel-level engine per D12 [src: HOS-Webdoc/web/src/data/hos-specification.ts:589].

Triad flow

flowchart LR
  subgraph GENOME ["GENOME — what it is (data)"]
    G["genome.json strand<br/>traits · theme · districts · pages<br/>+ spatial_site strand"]
  end
  subgraph COGNI ["COGNI — understanding (rules)"]
    C["per-engine cogni entries<br/>(Sapiens3 Datans · AH KG+Physics ·<br/>CLand Gateways/WebServices · DWork entropy→structure)"]
  end
  subgraph KERNEL ["KERNEL — code (contracts)"]
    K["engine contracts + env/keys<br/>chapters · slabs · manifest ·<br/>loaders · budgets"]
  end
  G -- "defines rules for" --> C
  C -- "runs on its own kernel" --> K
  K -- "renders/executes; results hash back" --> G
  NW["Neuralwares<br/>(equipped plug-ins)"] -. "injected into the sequence" .-> K

How a spatial-site instance is born

Read top-down; every arrow is a loop with a commit (pb-001-spatial-site-loop).

flowchart TD
  A["1 · GENOME<br/>venture genome.json (23 keys) + spatial_site strand:<br/>biome · slices · holonprints · camera_paths<br/>[[schema-genome-spatial-strand]]"]
  B["2 · COGNI RULES<br/>cogni-spatial-site: which engine does what for this instance<br/>(CLand renders districts; AH composes data;<br/>DWork schedules; Sapiens3 staffs Datans)"]
  C2["3 · KERNEL CONTRACTS<br/>kernel-spatial-site: ChapterId map · CHAPTER_SLABS ·<br/>SplatManifest · THEME_ARC · SPLAT_BUDGET"]
  D2["4 · GENERATION LOOPS<br/>squads bake assets per holonprint contracts<br/>(method: gaussian-splatting first)"]
  E["5 · LIVE INSTANCE<br/>scroll-film + PAD/POD surfaces;<br/>content_hash verifies the strand"]
  A -->|"genome → kernel is deterministic:<br/>strand keys select contracts"| C2
  A -->|"strand cogni[] entries"| B
  B -->|"gate: method → execute"| D2
  C2 --> D2
  D2 --> E
  E -.->|"telemetry + new holons write back"| A

Concrete anchors: the Royal Orbit strand carries genome_strand.content_hash: "sha256:471297f30f5e1678" [src: wiki/organizations/instances/royalorbit/genome.json:50] and per-engine cogni entries (e.g. CodeLand: "API Gateways for PADs · WebServices for PODs", kernel "the element ladder: SPOT · SITE · DISTRICT · BIOM · SPACE") [src: wiki/organizations/instances/royalorbit/genome.json:70]; the spatial-site kernel contracts live in @hos/engine [src: HOS-Instance/packages/engine/src/engine/contracts.ts:1]. Determinism note: LLM-backed steps are not bit-reproducible — "Determinism comes from the Cognitive Loop gate …, strict Cogni schemas, and the Genome hash/verify" [src: wiki/engines/cognitive-loop.md:102].

Composition

See also

Linked from — 19 cards