Unified Categorical Language System

Example Name:
Registry: —
Anchor Kind: —
Validity Function: N/A
Priority Rule: Not applicable / meta
Governance Action: Meta-governance; cross-code harmonization
Semantics: Umbrella for formal rules governing scientific names across organismal groups (contextual family of codes).
Pragmatics: Used to standardize naming, ensure stability, and enable global scientific communication.
Etymology: Latin: inter (“between”) + natio (“people, nation”); codex (“book of laws”); nomen (“name”) + calare (“to call”) → nomenclatura.
UCLS Mapping: Meta-token: family of rule-grammars; governs validity, priority, and anchor semantics across subcodes.

Example Name: Quercus robur (ICN binomial)
Registry: —
Anchor Kind: Type specimen/illustration (botanical)
Validity Function: Effective publication + typification; fungi require registration (MycoBank/IF/Fungal Names)
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: Conservation/Rejection; Nomenclature Section decisions; Chapter F updates
Semantics: The botanical code for algae, fungi, and plants (incl. fossils).
Pragmatics: Primary legal-grammar for plant/fungal names; mandates typification and (for fungi) registration.
Etymology: Modern acronym from code title.
UCLS Mapping: Rule set: rank grammar + type anchors; registry edges to MycoBank/IndexFungorum/Fungal Names.

Example Name: Quercus robur (ICN binomial)
Registry: —
Anchor Kind: Type specimen/illustration (botanical)
Validity Function: Effective publication + typification; fungi require registration (MycoBank/IF/Fungal Names)
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: Conservation/Rejection; Nomenclature Section decisions; Chapter F updates
Semantics: Full expansion of ICNafp; includes Chapter F for fungi.
Pragmatics: Source of rules for botanical/fungal naming, conservation, and rejection.
Etymology: Latinate scientific register with Greek roots (alga, mykes, planta).
UCLS Mapping: Same as ICNafp; explicit scope nodes for algae/fungi/plants.

Example Name: Quercus robur (ICN binomial)
Registry: —
Anchor Kind: —
Validity Function: N/A
Priority Rule: Not applicable / meta
Governance Action: Meta-governance; cross-code harmonization
Semantics: Scholarly association supporting plant taxonomy and the ICNafp ecosystem.
Pragmatics: Maintains resources, publications, and community governance support.
Etymology: Greek: taxis + nomos → taxonomy; modern acronym.
UCLS Mapping: Governance node; edges to code maintenance and publication channels.

Example Name: Quercus robur (ICN binomial)
Registry: —
Anchor Kind: —
Validity Function: N/A
Priority Rule: Not applicable / meta
Governance Action: Meta-governance; cross-code harmonization
Semantics: Global congress that convenes the Nomenclature Section to amend ICNafp.
Pragmatics: Formal venue where rule changes are debated and ratified.
Etymology: Greek botane (“plant”); Latin congressus (“coming together”).
UCLS Mapping: Procedure controller; change-management authority in the ledger.

Example Name: Quercus robur (ICN binomial)
Registry: —
Anchor Kind: Type specimen/illustration (botanical)
Validity Function: Effective publication + typification; fungi require registration (MycoBank/IF/Fungal Names)
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: Conservation/Rejection; Nomenclature Section decisions; Chapter F updates
Semantics: Fungal-specific chapter of ICNafp maintained via IMC.
Pragmatics: Imposes registration and other fungal naming requirements.
Etymology: Latin capitulum (“little head”) → chapter; letter “F”.
UCLS Mapping: Scoped rule module; registry constraint hook for fungal names.

Example Name: Quercus robur (ICN binomial)
Registry: —
Anchor Kind: —
Validity Function: Effective publication + typification; fungi require registration (MycoBank/IF/Fungal Names)
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: Conservation/Rejection; Nomenclature Section decisions; Chapter F updates
Semantics: Recent editions: Maastricht (Chapter F 2024) and Madrid (ICN 2025).
Pragmatics: Labels for current operative texts; cite in compliance checks.
Etymology: Place-name origins; Latin codex.
UCLS Mapping: Versioning tokens; bind rules to edition timestamps.

Example Name: Quercus robur (ICN binomial)
Registry: https://www.mycobank.org
Anchor Kind: Type specimen/illustration (botanical)
Validity Function: Effective publication + typification; fungi require registration (MycoBank/IF/Fungal Names)
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: Conservation/Rejection; Nomenclature Section decisions; Chapter F updates
Semantics: Fungal name registration database.
Pragmatics: Required for valid publication of fungal names.
Etymology: Greek mykes (“fungus”); English “bank”.
UCLS Mapping: Registry node; satisfies validity predicate for fungi.

Example Name: Quercus robur (ICN binomial)
Registry: https://www.indexfungorum.org
Anchor Kind: Type specimen/illustration (botanical)
Validity Function: Effective publication + typification; fungi require registration (MycoBank/IF/Fungal Names)
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: Conservation/Rejection; Nomenclature Section decisions; Chapter F updates
Semantics: Authoritative fungal name index.
Pragmatics: Cross-checks synonymy and nomenclatural status.
Etymology: Latin index + fungorum (genitive plural, “of fungi”).
UCLS Mapping: Authority edge for reconciliation and synonym control.

Example Name: Quercus robur (ICN binomial)
Registry: https://www.fungalinfo.net/fungalnames/
Anchor Kind: Type specimen/illustration (botanical)
Validity Function: Effective publication + typification; fungi require registration (MycoBank/IF/Fungal Names)
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: Conservation/Rejection; Nomenclature Section decisions; Chapter F updates
Semantics: Recognized fungal registration system.
Pragmatics: Alternative registration route alongside MycoBank/IndexFungorum.
Etymology: English with Latin root.
UCLS Mapping: Parallel registry node; redundancy increases resilience.

Example Name: Quercus robur (ICN binomial)
Registry: —
Anchor Kind: Type specimen/illustration (botanical)
Validity Function: Effective publication + typification; fungi require registration (MycoBank/IF/Fungal Names)
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: Conservation/Rejection; Nomenclature Section decisions; Chapter F updates
Semantics: Act of linking a name to a type exemplar.
Pragmatics: Primary anchor for identity in nomenclature.
Etymology: Greek typos → Latin typus → English “type” + -fication.
UCLS Mapping: Anchor operation; sets semantic pointer for tokens.

Example Name: Quercus robur (ICN binomial)
Registry: —
Anchor Kind: —
Validity Function: Effective publication + typification; fungi require registration (MycoBank/IF/Fungal Names)
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: Conservation/Rejection; Nomenclature Section decisions; Chapter F updates
Semantics: Minimum criteria for a work to count for naming purposes.
Pragmatics: Gate in the validity function for names.
Etymology: Latin efficere; publicare.
UCLS Mapping: Validity predicate input (publication channel).

Example Name: Quercus robur (ICN binomial)
Registry: —
Anchor Kind: —
Validity Function: Effective publication + typification; fungi require registration (MycoBank/IF/Fungal Names)
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: Conservation/Rejection; Nomenclature Section decisions; Chapter F updates
Semantics: Earliest compliant name is the correct one unless conserved.
Pragmatics: Ensures stability via historical precedence.
Etymology: Latin prior; principium.
UCLS Mapping: Ordering operator in conflict resolution.

Example Name: Quercus robur (ICN binomial)
Registry: —
Anchor Kind: —
Validity Function: Effective publication + typification; fungi require registration (MycoBank/IF/Fungal Names)
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: Conservation/Rejection; Nomenclature Section decisions; Chapter F updates
Semantics: Formal acts to stabilize usage by conserving or rejecting names.
Pragmatics: Override mechanism to protect stability and clarity.
Etymology: Latin servare (“to keep”); iacere (“to throw”).
UCLS Mapping: Governance action functions (override operators).

Example Name: Homo sapiens (ICZN binomial)
Registry: —
Anchor Kind: Name-bearing type (specimen/series)
Validity Function: Effective publication + ZooBank registration for e-only + availability criteria
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICZN Opinions & Declarations
Semantics: Zoological code governing animal names.
Pragmatics: Controls availability, types, and priority for animals.
Etymology: Modern acronym from code title.
UCLS Mapping: Rule set: rank grammar + ZooBank registration for e-works.

Example Name: Homo sapiens (ICZN binomial)
Registry: —
Anchor Kind: Name-bearing type (specimen/series)
Validity Function: Effective publication + ZooBank registration for e-only + availability criteria
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICZN Opinions & Declarations
Semantics: Full title of ICZN.
Pragmatics: Source of zoological naming law-grammar.
Etymology: Greek zoion; logos; Latin nomenclatura.
UCLS Mapping: Same as ICZN.

Example Name: Homo sapiens (ICZN binomial)
Registry: —
Anchor Kind: —
Validity Function: Effective publication + ZooBank registration for e-only + availability criteria
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICZN Opinions & Declarations
Semantics: Commission that interprets the Code and issues binding Opinions.
Pragmatics: Final arbiter for stability decisions in animal nomenclature.
Etymology: Latin commissio; Greek/Latin roots for scientific terms.
UCLS Mapping: Adjudication node; emits override operators (Opinions).

Example Name: Homo sapiens (ICZN binomial)
Registry: —
Anchor Kind: Name-bearing type (specimen/series)
Validity Function: Effective publication + ZooBank registration for e-only + availability criteria
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICZN Opinions & Declarations
Semantics: Type specimen or series carrying the name’s objective application (ICZN).
Pragmatics: Fixes the usage of a zoological name.
Etymology: Old English/Greek roots.
UCLS Mapping: Anchor artifact; pointer for token resolution.

Example Name: Homo sapiens (ICZN binomial)
Registry: https://zoobank.org
Anchor Kind: Name-bearing type (specimen/series)
Validity Function: Effective publication + ZooBank registration for e-only + availability criteria
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICZN Opinions & Declarations
Semantics: Official ICZN registry for nomenclatural acts and publications.
Pragmatics: E-only works require registration to be available.
Etymology: Greek zoion; English “bank”.
UCLS Mapping: Registry node; part of validity predicate for animals.

Example Name: Homo sapiens (ICZN binomial)
Registry: —
Anchor Kind: —
Validity Function: Effective publication + ZooBank registration for e-only + availability criteria
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICZN Opinions & Declarations
Semantics: Resolves synonym conflicts in zoology.
Pragmatics: Establishes name precedence in zoological nomenclature.
Etymology: Latin principium; prior.
UCLS Mapping: Ordering operator (zoological domain).

Example Name: Escherichia coli (type strain DSM 30083)
Registry: —
Anchor Kind: Type strain (culture)
Validity Function: Valid publication in IJSEM or via Validation Lists + type strain deposition
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICSP Judicial Commission Opinions; Validation Lists
Semantics: Code for Bacteria and Archaea.
Pragmatics: Defines valid publication routes and type strains.
Etymology: Modern acronym.
UCLS Mapping: Rule set: rank grammar + type strain deposit requirements.

Example Name: Escherichia coli (type strain DSM 30083)
Registry: —
Anchor Kind: Type strain (culture)
Validity Function: Valid publication in IJSEM or via Validation Lists + type strain deposition
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICSP Judicial Commission Opinions; Validation Lists
Semantics: Full title of ICNP.
Pragmatics: Source rules for prokaryotic names.
Etymology: Greek karyon; Latin nomenclatura.
UCLS Mapping: Same as ICNP.

Example Name: Escherichia coli (type strain DSM 30083)
Registry: —
Anchor Kind: —
Validity Function: Valid publication in IJSEM or via Validation Lists + type strain deposition
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICSP Judicial Commission Opinions; Validation Lists
Semantics: Governs ICNP; oversees Judicial Commission.
Pragmatics: Publishes opinions and validation mechanisms.
Etymology: Greek systema; karyon.
UCLS Mapping: Governance node; issues binding interpretations.

Example Name: Escherichia coli (type strain DSM 30083)
Registry: https://www.microbiologyresearch.org/content/journal/ijsem
Anchor Kind: —
Validity Function: Valid publication in IJSEM or via Validation Lists + type strain deposition
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICSP Judicial Commission Opinions; Validation Lists
Semantics: Primary venue for valid publication/Validation Lists under ICNP.
Pragmatics: Publication channel in the validity predicate for prokaryotes.
Etymology: Modern acronym.
UCLS Mapping: Channel node; feeds validation pipeline.

Example Name: Escherichia coli (type strain DSM 30083)
Registry: https://www.microbiologyresearch.org/content/journal/ijsem/val_list
Anchor Kind: —
Validity Function: Valid publication in IJSEM or via Validation Lists + type strain deposition
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICSP Judicial Commission Opinions; Validation Lists
Semantics: Official lists that make prokaryote names validly published.
Pragmatics: Backstop for names not originally in IJSEM proper.
Etymology: Latin validus; English “list”.
UCLS Mapping: Validation operator output; flips availability → valid.

Example Name: Escherichia coli (type strain DSM 30083)
Registry: —
Anchor Kind: Type strain (culture)
Validity Function: Valid publication in IJSEM or via Validation Lists + type strain deposition
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICSP Judicial Commission Opinions; Validation Lists
Semantics: Reference culture defining a prokaryote taxon.
Pragmatics: Must be deposited in certified collections (often ≥2 countries).
Etymology: Greek typos; English “strain”.
UCLS Mapping: Anchor artifact; culture-based pointer.

Example Name: Escherichia coli (type strain DSM 30083)
Registry: —
Anchor Kind: Type strain (culture)
Validity Function: Valid publication in IJSEM or via Validation Lists + type strain deposition
Priority Rule: Principle of Priority; conservation/suppression possible
Governance Action: ICSP Judicial Commission Opinions; Validation Lists
Semantics: Provisional status for uncultured but characterized prokaryotes.
Pragmatics: Reserves a taxonomic slot pending cultivation.
Etymology: Latin candidatus (“clothed in white”).
UCLS Mapping: Modality flag; provisional node awaiting anchor.

Example Name: Betacoronavirus 1 (ICTV binomial species)
Registry: https://ictv.global/
Anchor Kind: Exemplar isolate/sequence
Validity Function: Listed in ICTV Master Species List; compliance with ICTV naming rules
Priority Rule: ICTV-governed precedence via Master Species List updates
Governance Action: ICTV Taxonomy & Code updates
Semantics: Virus naming and classification rules.
Pragmatics: Defines ranks/suffixes; binomial species names.
Etymology: Modern acronyms.
UCLS Mapping: Rule set with sequence-centric anchors.

Example Name: Betacoronavirus 1 (ICTV binomial species)
Registry: https://ictv.global/
Anchor Kind: Exemplar isolate/sequence
Validity Function: Listed in ICTV Master Species List; compliance with ICTV naming rules
Priority Rule: ICTV-governed precedence via Master Species List updates
Governance Action: ICTV Taxonomy & Code updates
Semantics: Body that maintains virus taxonomy and nomenclature.
Pragmatics: Publishes Master Species List and Code updates.
Etymology: Greek taxis + nomos.
UCLS Mapping: Governance node; emits taxonomy datasets.

Example Name: Betacoronavirus 1 (ICTV binomial species)
Registry: —
Anchor Kind: —
Validity Function: Listed in ICTV Master Species List; compliance with ICTV naming rules
Priority Rule: ICTV-governed precedence via Master Species List updates
Governance Action: ICTV Taxonomy & Code updates
Semantics: Umbrella union under which ICTV operates.
Pragmatics: Institutional context for virus taxonomy governance.
Etymology: Modern acronym.
UCLS Mapping: Context node (organizational parent).

Example Name: Betacoronavirus 1 (ICTV binomial species)
Registry: —
Anchor Kind: Exemplar isolate/sequence
Validity Function: Listed in ICTV Master Species List; compliance with ICTV naming rules
Priority Rule: ICTV-governed precedence via Master Species List updates
Governance Action: ICTV Taxonomy & Code updates
Semantics: Genus + specific epithet naming convention.
Pragmatics: Reduces ambiguity; lingua franca across languages.
Etymology: Latin roots.
UCLS Mapping: Grammar template; head (genus) + dependent (epithet).

Example Name: Betacoronavirus 1 (ICTV binomial species)
Registry: https://ictv.global/
Anchor Kind: Exemplar isolate/sequence
Validity Function: Listed in ICTV Master Species List; compliance with ICTV naming rules
Priority Rule: ICTV-governed precedence via Master Species List updates
Governance Action: ICTV Taxonomy & Code updates
Semantics: Authoritative list of accepted virus species and metadata.
Pragmatics: Ground truth table for ICTV names and changes.
Etymology: English terms; Latin species.
UCLS Mapping: Dataset node; feeds registry/validation edges.

Example Name: Betacoronavirus 1 (ICTV binomial species)
Registry: https://ictv.global/
Anchor Kind: Exemplar isolate/sequence
Validity Function: Listed in ICTV Master Species List; compliance with ICTV naming rules
Priority Rule: ICTV-governed precedence via Master Species List updates
Governance Action: ICTV Taxonomy & Code updates
Semantics: ICTV repository of exemplar isolates/sequences and metadata.
Pragmatics: Provides anchor proxies when physical types are impractical.
Etymology: Latin virus (“poison”); Greek meta.
UCLS Mapping: Anchor registry (sequence-based).

Example Name: Rosa 'Peace' (cultivar epithet)
Registry: —
Anchor Kind: Cultivar description & registration record
Validity Function: Published denomination + ICRA registration/check
Priority Rule: Denomination priority within cultivar class (ICRA oversight)
Governance Action: ICRA determinations; ICNCP revisions
Semantics: Naming rules for cultivars and cultivar groups.
Pragmatics: Interfaces scientific taxonomy with horticultural trade.
Etymology: Modern acronym.
UCLS Mapping: Rule set: denomination classes + ICRA checks.

Example Name: Rosa 'Peace' (cultivar epithet)
Registry: —
Anchor Kind: Cultivar description & registration record
Validity Function: Published denomination + ICRA registration/check
Priority Rule: Denomination priority within cultivar class (ICRA oversight)
Governance Action: ICRA determinations; ICNCP revisions
Semantics: Full title of ICNCP.
Pragmatics: Defines cultivar epithet syntax and registration.
Etymology: Latin colere; planta.
UCLS Mapping: Same as ICNCP.

Example Name: Rosa 'Peace' (cultivar epithet)
Registry: https://www.ishs.org/scripta-horticulturae/icra
Anchor Kind: —
Validity Function: Published denomination + ICRA registration/check
Priority Rule: Denomination priority within cultivar class (ICRA oversight)
Governance Action: ICRA determinations; ICNCP revisions
Semantics: Society connected with ICNCP oversight and ICRA network.
Pragmatics: Coordinates cultivar registration authorities.
Etymology: Latin roots for horticulture.
UCLS Mapping: Governance node; registry coordination.

Example Name: Rosa 'Peace' (cultivar epithet)
Registry: https://www.ishs.org/scripta-horticulturae/icra
Anchor Kind: Cultivar description & registration record
Validity Function: Published denomination + ICRA registration/check
Priority Rule: Denomination priority within cultivar class (ICRA oversight)
Governance Action: ICRA determinations; ICNCP revisions
Semantics: Authority managing names in a cultivar denomination class.
Pragmatics: Prevents duplicate cultivar names; validates usage.
Etymology: Modern acronym.
UCLS Mapping: Registry gateway; denomination guardrail.

Example Name: Rosa 'Peace' (cultivar epithet)
Registry: —
Anchor Kind: Cultivar description & registration record
Validity Function: Published denomination + ICRA registration/check
Priority Rule: Denomination priority within cultivar class (ICRA oversight)
Governance Action: ICRA determinations; ICNCP revisions
Semantics: Non-Latinized name in single quotes for a cultivated plant variety.
Pragmatics: Bridges scientific and commercial naming.
Etymology: Latin/Greek roots.
UCLS Mapping: Name-form token; linked to ICRA registry node.

Example Name: Fagetum sylvaticae (syntaxon; example pattern)
Registry: —
Anchor Kind: Type relevé (community record)
Validity Function: Published description + type relevé + compliance with ICPN
Priority Rule: Priority within syntaxon rules; typified by relevé
Governance Action: IAVS Working Group decisions
Semantics: Rules for naming plant communities (syntaxa).
Pragmatics: Extends nomenclature above organismal taxa.
Etymology: Greek phyton (“plant”) + socius (“companion”).
UCLS Mapping: Rule set for ecosystem-level tokens.

Example Name: Fagetum sylvaticae (syntaxon; example pattern)
Registry: —
Anchor Kind: —
Validity Function: Published description + type relevé + compliance with ICPN
Priority Rule: Priority within syntaxon rules; typified by relevé
Governance Action: IAVS Working Group decisions
Semantics: Association linked to ICPN governance.
Pragmatics: Hosts working group for nomenclature of syntaxa.
Etymology: Latin vegetare (“to enliven”); English “science”.
UCLS Mapping: Governance node; standards custodian.

Example Name: Fagetum sylvaticae (syntaxon; example pattern)
Registry: —
Anchor Kind: Type relevé (community record)
Validity Function: Published description + type relevé + compliance with ICPN
Priority Rule: Priority within syntaxon rules; typified by relevé
Governance Action: IAVS Working Group decisions
Semantics: Named plant community unit under ICPN.
Pragmatics: Used in vegetation mapping/classification.
Etymology: Greek syntaxis (“arrangement”) + suffix -on.
UCLS Mapping: Token type: ecosystem-level category with type relevé.

Example Name: Fagetum sylvaticae (syntaxon; example pattern)
Registry: —
Anchor Kind: Type relevé (community record)
Validity Function: Published description + type relevé + compliance with ICPN
Priority Rule: Priority within syntaxon rules; typified by relevé
Governance Action: IAVS Working Group decisions
Semantics: Plot-based description serving as type for a syntaxon.
Pragmatics: Empirical anchor for plant community names.
Etymology: French relever (“to record/raise”).
UCLS Mapping: Anchor artifact (community holotype).

Example Name: Fagetum sylvaticae (syntaxon; example pattern)
Registry: —
Anchor Kind: Type relevé (community record)
Validity Function: Published description + type relevé + compliance with ICPN
Priority Rule: Priority within syntaxon rules; typified by relevé
Governance Action: IAVS Working Group decisions
Semantics: Primary name-bearing relevé/specimen for a taxon or syntaxon.
Pragmatics: Fixes application of a name unambiguously.
Etymology: Greek holos (“whole”) + typos (“type”).
UCLS Mapping: Anchor artifact; canonical pointer.

Example Name: Aves (node-based clade definition)
Registry: —
Anchor Kind: Phylogenetic specifiers
Validity Function: Definition published + RegNum registration with specifiers
Priority Rule: Definition-based stability; priority secondary to registration
Governance Action: PhyloCode Commission decisions; RegNum registration
Semantics: Rank-free code for clade names defined by phylogenetic relationships.
Pragmatics: Names track definitions, not Linnaean ranks.
Etymology: Greek phylē (“tribe”) + English “code”.
UCLS Mapping: Definition-grammar over graphs; uses specifiers.

Example Name: Aves (node-based clade definition)
Registry: —
Anchor Kind: Phylogenetic specifiers
Validity Function: Definition published + RegNum registration with specifiers
Priority Rule: Definition-based stability; priority secondary to registration
Governance Action: PhyloCode Commission decisions; RegNum registration
Semantics: Formal title of the PhyloCode.
Pragmatics: Specifies clade name definitions and registration.
Etymology: Greek phylē (“clan”), genesis (“origin”).
UCLS Mapping: Same as PhyloCode with RegNum registration.

Example Name: Aves (node-based clade definition)
Registry: —
Anchor Kind: Phylogenetic specifiers
Validity Function: Definition published + RegNum registration with specifiers
Priority Rule: Definition-based stability; priority secondary to registration
Governance Action: PhyloCode Commission decisions; RegNum registration
Semantics: Monophyletic group defined by common ancestry.
Pragmatics: Used across systematics, evolutionary biology, and comparative methods.
Etymology: Greek klados (“branch”).
UCLS Mapping: Graph node-set; definable via node/branch/apomorphy.

Example Name: Aves (node-based clade definition)
Registry: https://www.phylocode.org/regnum/
Anchor Kind: Phylogenetic specifiers
Validity Function: Definition published + RegNum registration with specifiers
Priority Rule: Definition-based stability; priority secondary to registration
Governance Action: PhyloCode Commission decisions; RegNum registration
Semantics: Registration database for PhyloCode names.
Pragmatics: Ensures uniqueness and versioning of clade definitions.
Etymology: Constructed Latinate brand.
UCLS Mapping: Registry node; binds name to definition hash.

Example Name: Aves (node-based clade definition)
Registry: —
Anchor Kind: Phylogenetic specifiers
Validity Function: Definition published + RegNum registration with specifiers
Priority Rule: Definition-based stability; priority secondary to registration
Governance Action: PhyloCode Commission decisions; RegNum registration
Semantics: Clade defined by most recent common ancestor of specified taxa.
Pragmatics: Stable under tree updates if specifiers remain valid.
Etymology: Latin nodus (“knot”); definire (“to set limits”).
UCLS Mapping: Logical formula over DAG with specifier anchors.

Example Name: Aves (node-based clade definition)
Registry: —
Anchor Kind: Phylogenetic specifiers
Validity Function: Definition published + RegNum registration with specifiers
Priority Rule: Definition-based stability; priority secondary to registration
Governance Action: PhyloCode Commission decisions; RegNum registration
Semantics: Clade defined by ancestry including species X but excluding Y.
Pragmatics: Tracks lineage inclusion/exclusion explicitly.
Etymology: Old French branche; Latin definire.
UCLS Mapping: Set-builder rule over phylogeny.

Example Name: Aves (node-based clade definition)
Registry: —
Anchor Kind: Phylogenetic specifiers
Validity Function: Definition published + RegNum registration with specifiers
Priority Rule: Definition-based stability; priority secondary to registration
Governance Action: PhyloCode Commission decisions; RegNum registration
Semantics: Clade defined by possession of a specified derived character.
Pragmatics: Connects character matrices to nomenclature semantics.
Etymology: Greek apo (“away”) + morphē (“form”).
UCLS Mapping: Predicate over character state space.

Example Name: —
Registry: —
Anchor Kind: —
Validity Function: N/A
Priority Rule: Not applicable / meta
Governance Action: Meta-governance; cross-code harmonization
Semantics: Organization empowered to interpret and maintain a code.
Pragmatics: Issues opinions, updates, and conservation actions.
Etymology: Latin gubernare (“steer”) + Old English bodig (“body”).
UCLS Mapping: Authority node; emits rule changes and overrides.

Example Name: —
Registry: —
Anchor Kind: —
Validity Function: N/A
Priority Rule: Not applicable / meta
Governance Action: Meta-governance; cross-code harmonization
Semantics: Recording a name/act in an official registry.
Pragmatics: Prerequisite for validity in several codes (e.g., fungi, ZooBank).
Etymology: Latin registrum (“list, record”).
UCLS Mapping: Validity predicate input (registry edge present).

Example Name: —
Registry: —
Anchor Kind: —
Validity Function: N/A
Priority Rule: Not applicable / meta
Governance Action: Meta-governance; cross-code harmonization
Semantics: Same concept as “Effective Publication” under ICNafp; listed separately to preserve the set.
Pragmatics: Duplicate signal: map to same validity gate in UCLS.
Etymology: Latin roots as above.
UCLS Mapping: Alias → canonical predicate.

Example Name: —
Registry: —
Anchor Kind: —
Validity Function: N/A
Priority Rule: Not applicable / meta
Governance Action: Meta-governance; cross-code harmonization
Semantics: Goal of nomenclature: names remain reliable across time.
Pragmatics: Motivates priority, conservation, and formal procedures.
Etymology: Latin stabilis (“firm, stable”).
UCLS Mapping: Objective function; quality metric over name graph.

Example Name: —
Registry: —
Anchor Kind: —
Validity Function: N/A
Priority Rule: Not applicable / meta
Governance Action: Meta-governance; cross-code harmonization
Semantics: Names intelligible and usable across languages and regions.
Pragmatics: Supports interoperability and cross-disciplinary use.
Etymology: Latin universalis (“universal”).
UCLS Mapping: Design constraint; cross-lingual mapping rule.

Example Name: —
Registry: —
Anchor Kind: —
Validity Function: N/A
Priority Rule: Not applicable / meta
Governance Action: Meta-governance; cross-code harmonization
Semantics: Imposition of uniform formats and procedures for names.
Pragmatics: Enables automation, registries, and legal adoption.
Etymology: Old French estandard (“standard”) + verb-forming -ize + noun-forming -ation.
UCLS Mapping: Normalization function in ingestion/validation pipeline.