Privacy and analytics

We use necessary technical cookies and, only with your consent, analytics and marketing pixels to improve the website and measure campaigns.

Privacy policyCookie policy
Docs
English
EspañolEnglishFrançaisDeutschItalianoPortuguês

Getting started

  • What is Nömad?
  • Getting started with Nömad
  • Create your brand and complete the Genome
  • Invite your team
  • Glossary

Brand OS

  • What is inside Brand OS
  • What is the Genome?
  • Who is Nödo?
  • What does a Brand Manager do?
  • Brand Kit and Library
  • Posts and calendar
  • Connections
  • Meetings

Work

  • Work and tasks
  • Ordering work
  • Following, reviewing and approving deliveries
  • Custom quotes
  • Yes, there are humans behind it

Account and billing

  • Plans and pricing
  • Billing and payments
  • Roles and permissions
  • Workspaces and multiple brands
  • Languages, apps and data

Help

  • How to get help

API

  • Brand API

MCP

  • MCP server

Connectors

  • Brand connectors

Nödo and agents

  • Nödo in the brand

Genome

  • Genome specification
    • Fields
    • Example
    • brand.json
Genome
Concept2 min read

Genome specification

The Genome 2.1 JSON format, its schemas and versioning rules.

On this page
  • Parts
  • Schemas
  • Versioning
  • Reading rules
  • History

Updated on January 1, 1970

Русский
한국어
日本語
中文
हिन्दी
Open the app
PreviousWidgets
NextFields
Can't find what you need? Write to usWrite to usGo to the app
© 2026 Nömad · Nömad documentationLinkedInInstagramFacebookTikTokYouTubeX
Go to nomad.oooBack to top

On this page

  • Parts
  • Schemas
  • Versioning
  • Reading rules
  • History

The Genome is the JSON document of a brand in Nömad: who the organisation is, how it looks, what it thinks and how it speaks. Nödo, the MCP server and the API read it, and BRAND.md, DESIGN.md, brand.json and the design tokens are generated from it. This specification is public and versioned so any tool can read and validate it.

Parts

MemberWhat it holds
schemaVersion, revisionMajor version of the format and revision of the document. Always present.
metadataOrganisation profile: type, industry, headquarters, size, business models, languages and public contact channels.
visualIdentityLogos, colours, typefaces and manuals composed from the brand's Library. Read-only in the Genome.
strategyThe strategy in fifteen sections, written in the brand's primary language.
assertionsWhich core data a person has confirmed (since 2.1).
provenanceWhere the profile and the visual identity come from.

Schemas

JSON Schema draft 2020-12, served with open CORS. Versioned URLs never change once published; the alias follows the latest 2.x.

DocumentURL
Genome 2.1https://docs.nomad.ooo/schemas/genome/v2.1.json
Genome 2.x (stable alias)https://docs.nomad.ooo/schemas/genome/v2.json
brand.json (nomad-brand/1)https://docs.nomad.ooo/schemas/brand/1.json

Versioning

  • schemaVersion holds only the major version (2). The specification version is major.minor: this is 2.1.
  • Minor versions only add: optional fields, new sections or new enum values. Within a major version nothing is removed, renamed or retyped.
  • Removing or changing anything requires a new major version, with its own schemaVersion and its own schema.
  • Validate with the latest schema of the document's major version (the v2.json alias).
  • revision is a per-document counter that grows with every saved change. Use it to tell whether the Genome changed since you last read it.

Reading rules

  • Only schemaVersion and revision are always there. Any other member may be absent: a section not generated yet, an older document or an excerpt. When it is absent, do not invent it.
  • Ignore members you do not know and treat an unknown enum value as other or unknown.
  • An empty string means unknown. The literal NO DISPONIBLE marks a field left empty for lack of evidence.
  • Only data with assertions.<path>.state = confirmed is the brand's truth; the rest are proposals a person has not confirmed yet.
  • Text in strategy is written in metadata.primaryLanguage; field names and enum values are in English.

History

VersionChanges
2.1First public version of the specification. Includes assertions (confirmation state of the core), the executable voice in verbalSystem (address, voiceExamples, sayDontSay, conventions, channelGuide) and the named offer in commercial.offerings.