Genome · genome

Owner directive (D8, 2026-04-12), canonical. "RESOLVED: Rename lib/dna/ → lib/genome/. Source: Lucas correction 'Genome is the new name for DNA'. GenomeStrand becomes the canonical type, DNAStrand is removed." [src: HOS-Webdoc/web/src/data/hos-specification.ts:557] — and per OWNER-2026-07-10: "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:473]

Content

Genome = the genetic blueprint that engines use to instance entities [src: wiki/architecture/genome.md:7]. It replaces the legacy DNA naming (D8, C-05: "Genome is the name. lib/dna/ is a legacy re-export only" [src: wiki/development/HANDOFF.md:137]). The Genome is the definition axis of the Kernel/Cogni/Genome triad: a genome defines an instance; the rule the live instance then runs is the cognitive-loop [src: wiki/architecture/genome.md:9].

Guiding principle: "database + schematic must regenerate the entire HOS, and 40 regenerations must give the same results" [src: wiki/architecture/genome.md:11]. Every entity carries a genome-strand; instanceFromGenome() walks the canonical 8-step pipeline (validate-genome → generate-infrastructure → create-districts → allocate-datans → wire-web-properties → register-hos → bootstrap-engines in order cland → sapiens3 → dwork → neural → atomicHolon → hash-content), returning a pure SpawnPlan with no side effects [src: wiki/architecture/genome.md:99-110].

For the spatial-site, the genome extends to environment definition — "everything related to the venture genome, their endeavors (programs, Products, Profissionalization) and Experience loops" [src: ...knowledge-management-and-concept-modeling.md:465] — encoded as schema-genome-spatial-strand with genome-spatial-site the instance card and genome-schema the base.

Known gaps (RUN-006, carried forward):

• "dispatchSpawnPlan() is presented as a real Coolify/DigitalOcean deployment bridge but does not exist anywhere in the codebase" [src: wiki/architecture/genome.md:154]. (A Fortress-lib implementation landed in concept-validation/lib during RUN-007.)
• "hashGenome does NOT sort keys recursively and silently drops nested fields, so semantically different genomes can collide to the same contentHash" [src: wiki/architecture/genome.md:155] — the determinism guarantee is overstated until fixed.

Composition

• uses: genome-strand (base type), districts (instanced children), squad + datan (allocation), engines (bootstrapped)
• used-by: entity-hierarchy (every entity carries one), holonprint (imprint axis feeds DatanGenome), spatial-site (genome-spatial-site), schema-genome-spatial-strand, sc-001-kernel-cogni-genome, venturebook / endeavorbook

See also

• genome-strand — the per-entity strand
• kernel · cogni — the other two axes of the triad
• [Upstream wiki page](../../../wiki/architecture/genome.md)