Genome JSON Schema (23-key contract) · genome-schema
D8 ruling (2026-04-12), canonical. "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] — confirmed by C-05: "Genome is the name.
lib/dna/is a legacy re-export only; new work targetslib/genome/." [src: wiki/development/HANDOFF.md:137]
Content
Every HOS instance is declared by one genome.json — "the genetic blueprint that engines use to instance entities" [src: wiki/architecture/genome.md:7]. The reference document is the Royal Orbit instance genome [src: wiki/organizations/instances/royalorbit/genome.json:1], generated from organizations-identities/royalorbit.json and regenerable (meta.regenerable: true) — the governing principle being that "database + schematic must regenerate the entire HOS, and 40 regenerations must give the same results" [src: wiki/architecture/genome.md:13]. Drift is detected by hashing: genome_strand.content_hash (e.g. "sha256:471297f30f5e1678" [src: wiki/organizations/instances/royalorbit/genome.json:50]).
The 23 top-level keys
| # | Key | Holds | [line] |
|---|---|---|---|
| 1 | instance | id, slug, name, type, status, os_layer, mission, one_liner, values, summary | 2 |
| 2 | genome_strand | the genome-strand core: id, entity_type, version, mobilizer-level, parent_os, traits, content_hash | 38 |
| 3 | cognis | the six engine rows (engine / layer / cogni / kernel / role_for_instance) — see cogni and engines | 52 |
| 4 | element_ladder | ELEMENT → COMPONENT → pad → pod → SPOT → SITE → DISTRICT → BIOM → SPACE | 96 |
| 5 | districts | named districts with rung + pods + source | 134 |
| 6 | programs | ventures/endeavors with kernels_used + endeavors[] | 232 |
| 7 | web_properties | Website / WebApp / WebSocial / WebDocs / WebIdentity (kind, route, stack, domain, concept) | 298 |
| 8 | theme | mode, variant, palette, typography, motion, layout, website_3d | 349 |
| 9 | websites | concrete site trees (domain, framework, pages[] with sections) | 402 |
| 10 | emails | domain, SPF/DKIM/DMARC state, addresses[] with purpose | 461 |
| 11 | domains | all domains | 495 |
| 12 | primary_domain | the canonical one | 500 |
| 13 | audiences | personas + segments | 501 |
| 14 | protocols | named workflows with steps (e.g. Gap review, PAD/POD context isolation) | 508 |
| 15 | development_plan | phases[] with goal + steps | 530 |
| 16 | pages | C/_ Framework Pages: biom, story, theme, soul, will, expertise, adventure, opportunity, define, prepare, visualize | 570 |
| 17 | market | TAM/SAM/SOM, positioning, timing, go_to_market, segments, competitors | 834 |
| 18 | web_identity | voice, biom, logo, communication | 867 |
| 19 | artifacts | named image/video/doc artifacts per page | 873 |
| 20 | assets | binary asset registry | 970 |
| 21 | hosts | rhosts + email-principals (every host with type + address) | 971 |
| 22 | versions | version, date, notes per evolution | 1028 |
| 23 | meta | generated_from, generated_at, regenerable | 1035 |
[all src: wiki/organizations/instances/royalorbit/genome.json]
The strand core (genome_strand)
The typed backbone is GenomeStrand in code: id, entityType, name, version ("bumped on every evolution"), mobilizerLevel ("BOT < ... < LOOPER"), traits (free-form bag), petraRules ("rule IDs this genome MUST satisfy at instantiation time" — see petra), createdAt/evolvedAt, contentHash ("detects drift between regenerations") [src: HOS-Webdoc/web/src/lib/genome/types.ts:37]. Entity types include venture, endeavor, datan, hyperHuman, organization, partner, looper, host, program, squad [src: HOS-Webdoc/web/src/lib/genome/types.ts:25].
Extension strands
The 23-key contract is extensible by named strands keyed under the genome. The first extension strand is spatial_site, documented in genome-spatial-site (typed form in schema-genome-spatial-strand); its worked instance is genome-spatial-site.example.json in this folder. Extension strands must themselves be regenerable and content-hashed, inheriting the D8/40-regenerations discipline.
Composition
- uses: genome-strand (core type), mobilizer-level (hierarchy field), petra (instantiation rules), entity-hierarchy (entity types), pad / pod (element ladder rungs)
- used-by: genome-spatial-site (the spatial extension strand), district-spatial-site (instanced from a genome), venturebook + endeavorbook (books drawing on
programsandmarket), sc-001-kernel-cogni-genome (schematic), kernel-neural-engine (dispatch references instance genomes)
See also
- genome — the concept card
- genome-spatial-site · schema-genome-spatial-strand
- [Genome (wiki canon)](../../../wiki/architecture/genome.md)
- [Royal Orbit instance genome](../../../wiki/organizations/instances/royalorbit/genome.json)