UCLS Universal Language Control Plane (ULCP)

0) First Principles (non-negotiables)

  • Token before thing. Names, notations, and labels are first-class. Things are reached through anchors.
  • Anchor or it didn’t happen. Every claim binds to a specimen/strain/sequence/relevé/credential/record.
  • Priority with provenance. Time, source, and legitimacy are embedded in every operation.
  • Governance is code. Opinions, ballots, and exceptions are machine-actionable and diffable.
  • Recursion everywhere. The same flow works at word, class, registry, and policy layers.

1) The Language Fabric (manages all language)

Scope: Terms, phrases, binomials, clade names, compound names, brand names, SKUs, codes, acronyms, translations, transliterations, symbols, units, scripts, and controlled labels across all sectors.

1.1 Services (core)

  • NaaS (Naming): normalize/mint names; manage variants, scripts, and morphology.
  • TLaaS (Translation/Localization): cross-lingual mappings; phoneme/morpheme overlays; romanization policies.
  • OaaS (Ontology): classes/relations; align to external vocabs; publish JSON-LD/OWL.
  • IDaaS (Identity): persistent IDs, handles, DOIs; alias/synonym graphs.
  • RaaS (Reconciliation): collapse duplicates; cross-registry concordance.
  • RegaaS (Registry): register & resolve records in domain registries.
  • ValaaS (Validation): SHACL/JSON-Schema; code-rule checks.
  • PRaaS/GaaS (Priority/Governance): priority, conservation/rejection, exceptions; ballots/opinions.
  • VaaS (Versioning): immutable snapshots, time-travel diffs.
  • ProvAaaS (Provenance & Audit): signatures, lineage, evidence trails.
  • InteropaaS: adapters (GBIF, NCBI, Crossref, ISO, OPC UA, XBRL, OGC, PDS4, HL7/FHIR, W3C VC…).
  • ACaaS (Access Control): RBAC/ABAC; VC-based selective disclosure.
  • DaaS/AnaaS/VizaaS: discovery, analytics, visualization.

1.2 Canonical Data Model (JSON-LD)

{
  "@context": ["https://ucls.org/context/core/v1"],
  "token": {
    "value": "Example token",
    "kind": "binomial|compound|deviceModel|term|...",
    "language": "la|en|ar|zh|...",
    "script": "Latn|Cyrl|Hans|...",
    "governedBy": "ICZN|ICNafp|ICNP|ICTV|ICPN|ICNCP|IUPAC|ISO|...",
    "etymology": "…",
    "variants": [{"form":"…","locale":"…","status":"preferred|alt|deprecated"}]
  },
  "anchor": {
    "kind": "typeSpecimen|typeStrain|sequence|cultivarRecord|releve|digitalCredential|legalRecord|instrumentDataset",
    "id": "DSM 30083|DOI:10.x|ORCID:…|IMEI:…|…",
    "registry": "DSMZ|ZooBank|ICTV|ICRA|Crossref|PDS|PKI|..."
  },
  "registryRecord": {"registry":"…","id":"…","uri":"https://…"},
  "governanceAction": {"type":"opinion|conservation|rejection|exception","by":"ICZN|ICSP|ICTV|IAPT|ISO|NERC|FDA|…","date":"YYYY-MM-DD"},
  "identifiers": {"ucls":"ucls:…","doi":"10.…","handle":"hdl:…"},
  "links": [{"rel":"sameAs|broader|narrower|exactMatch|closeMatch","href":"…"}]
}

1.3 SHACL (shape of truth, abbreviated)

  • token.value required; unique per governedBy + kind + language.
  • anchor.kind/id/registry required for any actionable claim.
  • governanceAction mutates status via PRaaS; every change writes a VaaS snapshot and ProvAaaS trail.

1.4 Primary Flow (sector-agnostic)

Token → AaaS anchor → ValaaS validity → RegaaS registration → PRaaS/GaaS (if conflict) → ProvAaaS audit → InteropaaS publish → DaaS discover → VaaS release.

1.5 SLO Palette (defaults)

  • Validity pass rate ≥ 99%
  • Identifier resolvability ≥ 99.9% within 300 ms
  • Synonym collapse lag < 7 days
  • Governance turnaround < 30 days (tunable)

1.6 Risk Controls (uniform)

  • Collisions: NaaS normalization + IDaaS uniqueness; PRaaS tie-breakers.
  • Staleness: RegaaS multi-home + periodic concordance; alert on drift.
  • Ambiguous anchors: AaaS provenance proof required; reject weak claims.
  • Policy drift: GaaS policy packs; VaaS-diffed rule snapshots with approvals.
  • PII/creds exposure: ACaaS ABAC + W3C VC selective disclosure.

2) API Surface (uniform across sectors)

POST /ucls/names                 # NaaS mint/normalize
POST /ucls/anchors               # AaaS bind token→anchor
POST /ucls/registrations         # RegaaS create/resolve
POST /ucls/validations           # ValaaS checks (code rules + SHACL)
POST /ucls/governance/opinions   # GaaS/PRaaS decisions
GET  /ucls/resolve?id=...        # IDaaS resolve IDs / synonyms
GET  /ucls/graph/search?q=...    # DaaS discovery
GET  /ucls/versions/{id}         # VaaS history/snapshots
GET  /ucls/prov/{id}             # ProvAaaS lineage

Interchange contexts: JSON-LD; sector adapters (HL7/FHIR, Darwin Core, EPCIS, XBRL, OPC UA, YANG, PDS4, OGC, JATS, GA4GH).


3) Governance (priority as code)

  • Event types: mint, bind, validate, register, opine, conserve, reject, exception, merge, deprecate, release.
  • Ballots: quorum, super-majority thresholds per code/body; emitted as signed JSON-LD with VCs.
  • Appeals: PRaaS queue with strict clocks; VaaS enforces read-only after release.

4) Sector Annex (all sectors in coherent template)

For each sector: Subdomains • Jobs-to-be-Done • Codes • Anchors • Registries • Governance • Standards • Data Products • Flow • Adapters • KPIs • Risks • Services Used • Service Matrix (✓)

4.1 Healthcare & Biomed

  • Subdomains: Clinical, Pathology, Public Health
  • Jobs: Pathogen naming; variant tracking; clinical terminology alignment
  • Codes: ICTV; ICNP; ICZN; ICNafp (medicinals)
  • Anchors: Exemplar sequence; type strain; name-bearing type; type specimen
  • Registries: ICTV MSL; Virus Metadata Resource; IJSEM/Validation Lists; culture collections; ZooBank; MycoBank
  • Governance: ICTV; ICSP; ICZN; ICNafp Nomenclature Section; WHO/ICD mapping
  • Standards: HL7/FHIR; GA4GH; DOIs; ORCID; JSON-LD/RDF/OWL; W3C VC
  • Products: Clinical KG; variant registry; nomenclature ledger
  • Flow: Specimen/sequence → AaaS → ValaaS → RegaaS → TaaS update → PRaaS (if conflict) → ProvAaaS → InteropaaS → DaaS
  • KPIs: turnaround_time; synonymy_rate; registry_coverage; lineage_completeness
  • Risks/Controls: collisions; stale registries; ambiguous anchors; policy drift; PII exposure
  • Services: All core ✓

4.2 Bioinformatics & Genomics

  • Jobs: Genome bins→valid taxa; clade definitions; cross-DB reconciliation
  • Codes: ICNP; ICTV; PhyloCode
  • Anchors: Type strain; exemplar sequence; phylo specifiers
  • Registries: NCBI/ENA/DDBJ; IJSEM; ICTV; RegNum
  • Standards: FAIR; FASTA/GenBank; DOIs; ORCID; JSON-LD/RDF
  • Flow: MAG/assembly → sequence anchor → ValaaS → RegaaS → TaaS/Phylo def → VaaS snapshot
  • KPIs/Risks/Services: as above (domain-tuned)

4.3 Agriculture & Food Systems

  • Jobs: Cultivar registration; pathogen naming; supply traceability
  • Codes: ICNafp; ICNCP; ICNP; ICTV; ICPN
  • Anchors: Type specimen; cultivar record; type strain; exemplar sequence; type relevé
  • Registries: ICRA; MycoBank/IndexFungorum/Fungal Names; culture collections; ICTV; vegetation DBs
  • Standards: GS1; ISO 8000; JSON-LD/RDF/DOIs
  • Flow: Cultivar description → AaaS → ValaaS/ICRA check → RegaaS → NaaS → supply InteropaaS

4.4 Environmental & Biodiversity

  • Jobs: Occurrence reconciliation; red list integration; community syntaxa
  • Codes: ICZN; ICNafp; ICNP (env); ICPN
  • Anchors: Type specimen; name-bearing type; type relevé
  • Registries: ZooBank; herbaria; GBIF; vegetation plots
  • Standards: Darwin Core; GBIF APIs; JSON-LD/RDF
  • Flow: Occurrence import → RaaS → NaaS normalization → TaaS attach → VizaaS maps

4.5 Energy Systems

  • Jobs: Asset ontologies; materials taxonomy; safety governance trails
  • Codes: Meta (chem/material extensions)
  • Anchors: Digital credentials; material samples
  • Registries: ISO/IEC refs; corporate asset ledgers
  • Standards: RDF/OWL; CFIHOS; OPC UA; ISO 15926; W3C VC
  • Flow: Asset → IDaaS → OaaS class → TaaS placement → ProvAaaS → InteropaaS→ CMMS

4.6 Telecom & Networking

  • Jobs: Device identity; service naming; topology taxonomy
  • Anchors: X.509 certs; device attestation
  • Registries: PKI/CA; GSMA/IMEI; internal service catalogs
  • Standards: JSON-LD/RDF; YANG; W3C VC; GS1 (IoT)
  • Flow: Device join → IDaaS → NaaS → OaaS/TaaS topology → ACaaS policy → ProvAaaS logs

4.7 Government & Public Policy

  • Jobs: Controlled vocabs; interagency registries; provenance trails
  • Anchors: Records; legal IDs; sequences/specimens in health contexts
  • Registries: National registries; DOIs; ORCID; ICTV (when relevant)
  • Standards: JSON-LD/RDF; OAuth2/OIDC; W3C VC; HL7/FHIR
  • Flow: Term registry → OaaS → RegaaS → InteropaaS → GaaS workflows → ProvAaaS

4.8 Legal & IP

  • Jobs: Name-priority evidence; sequence disclosure linkage; claim provenance
  • Anchors: Specimens/strains/sequences; legal docs as digital anchors
  • Registries: Patent offices; scientific registries
  • Governance: WIPO; national IP offices
  • Standards: DOIs; W3C VC; JSON-LD
  • Flow: Claim ingest → anchor match → ProvAaaS chain → PRaaS decision

4.9 Education & Research

  • Jobs: Collections digitization; naming curriculum; open registries
  • Anchors: Type specimen/strain/sequence; phylo specifiers; relevé; cultivar
  • Registries: ZooBank; MycoBank; RegNum; ICTV; ICRA
  • Standards: Darwin Core; JSON-LD; RDF/OWL; DOIs; ORCID
  • Flow: Specimen digitize → AaaS → RegaaS → TaaS attach → OaaS curriculum graphs

4.10 Finance & Insurance

  • Jobs: Entity identity; ESG biodiversity linkage; risk models tied to taxonomy
  • Anchors: Type specimen/relevé; sequences for outbreak risk
  • Registries: GBIF; conservation lists; ICTV (risk)
  • Governance: IFRS/ISSB for ESG mapping
  • Standards: XBRL; RDF; JSON-LD
  • Flow: Asset geo → ICPN overlay → risk model → AnaaS dashboards

4.11 Manufacturing & Supply Chain

  • Jobs: Material taxonomy; batch lineage; counterfeit prevention
  • Anchors: Batch certificates; cultures/sequences for biologics
  • Registries: GS1; DOIs; culture collections
  • Standards: GS1 EPCIS; RDF/JSON-LD; W3C VC
  • Flow: Batch → IDaaS → ProvAaaS → InteropaaS (EPCIS) → ACaaS policy → VaaS snapshots

4.12 Space & Aerospace

  • Jobs: Life-detection ontologies; materials taxonomy; mission provenance
  • Anchors: Instrument data anchors; sequences (if any)
  • Registries: Mission DOIs; PDS nodes
  • Standards: PDS4; RDF/JSON-LD; DOIs
  • Flow: Observation → anchor → ProvAaaS → OaaS/TaaS attach → VaaS release

4.13 Climate & Geoscience

  • Jobs: Community syntaxa overlays; isotopic anchors; policy interfaces
  • Anchors: Type relevé; specimen ties; isotope anchors
  • Registries: Vegetation DBs; GBIF; DOI repos
  • Standards: OGC; NetCDF; RDF/JSON-LD
  • Flow: Relevé → TaaS syntaxon attach → policy InteropaaS → VizaaS maps

4.14 Media & Publishing

  • Jobs: Controlled terminology; entity linking; registry-backed citations
  • Anchors: DOIs; registry IDs; specimen/strain/sequence references
  • Registries: Crossref; DataCite; domain registries
  • Standards: JATS; JSON-LD; DOI; ORCID
  • Flow: Manuscript → NaaS terms → RegaaS citations → ProvAaaS → VaaS version

4.15 AI & Software

  • Jobs: Ontology grounding; registry resolution; policy-aligned actions
  • Anchors: Digital claims linked to domain anchors
  • Registries: Handles/DOIs; domain registries
  • Standards: JSON-LD/RDF; SHACL; W3C VC
  • Flow: Prompt → OaaS grounding → NaaS normalization → RegaaS resolve → ACaaS check → ProvAaaS trail

4.16 Smart Cities & Infrastructure

  • Jobs: Asset naming; biodiversity overlays; compliance ledgers
  • Anchors: Digital certs; relevés/specimens for env layers
  • Registries: City asset DBs; GBIF/vegetation DBs
  • Standards: OGC; RDF; JSON-LD; W3C VC
  • Flow: Sensor → IDaaS → NaaS → OaaS/TaaS → InteropaaS → VizaaS map

4.17 Defense & Security (completed)

  • Subdomains: Biosurveillance, Supply Integrity
  • Jobs: Pathogen intel; supply lineage; credentialed actions
  • Codes: ICTV; ICNP; meta where needed
  • Anchors: Sequences; strains; specimens; digital credentials
  • Registries: ICTV; culture collections; PKI
  • Governance: National labs/standards; code bodies
  • Standards: STIX/TAXII; RDF/JSON-LD; W3C VC
  • Products: Threat KG; lineage ledgers
  • Flow: Sample → sequence → ValaaS → RegaaS → TaaS attach → ACaaS policy → ProvAaaS
  • KPIs: detection_latency; false_positive_rate; lineage_integrity

4.18 Pharma & Drug Discovery (new, integrated)

  • Subdomains: Discovery (HTS/HCS), CMC, Pharmacovigilance
  • Jobs: INN alignment; compound→target→indication graph; sequence/construct governance; trial registry concordance
  • Codes: ICNP/ICTV where bio-actives; IUPAC/INN naming; RxNorm/ATC mapping
  • Anchors: Compound records (InChIKey/SMILES/SDfile); batch lots; expression constructs (sequences); trial IDs
  • Registries: CAS; PubChem; ChEMBL; UniProt; ClinicalTrials.gov; WHO INN; EMA/FDA submissions
  • Governance: WHO INN; FDA/EMA; ICH; ICSP/ICTV when applicable
  • Standards: HL7/FHIR (Medication/Ingredient); CDISC; SDF/SMILES/InChI; JSON-LD; DOIs; ORCID
  • Products: Compound→Target→Pathway KG; lot lineage; label/insert registry; safety signal graph
  • Flow: Token (INN/IUPAC) → AaaS (compound/batch/sequence) → ValaaS (ICH rules) → RegaaS (INN/RxNorm/CAS/ClinicalTrials) → PRaaS (name conflicts) → VaaS release
  • KPIs: structure_dedup_rate; lot_lineage_completeness; signal_detection_latency
  • Risks: name collisions; off-label ambiguity; disclosure drift → Controls: strict NaaS normalization; ProvAaaS on submissions; ACaaS on PII/PHI

5) Cross-Cutting Operating Model

5.1 Namespaces & IDs

  • ucls:{sector}:{kind}:{hash} (128-bit truncated hash of normalized token+context)
  • Resolve via GET /ucls/resolve?id=… with alias maps for DOI/Handle/CAS/ORCID/IMEI/etc.

5.2 Policy Packs (examples)

  • BioCode Pack: ICTV/ICNP/ICZN/ICNafp checks; IJSEM/Validation List gates.
  • Civic Pack: OIDC realm trust; record retention; audit immutability.
  • Industrial Pack: ISO 15926/OPC UA node sanity; EPCIS event integrity.
  • Clinical Pack: HL7/FHIR value set bindings; ICD/SNOMED crosswalks.

5.3 Quality Gates (per release)

  • Green: ≥99.5% concordance across registries; no unresolved collisions.
  • Yellow: Collisions < 50 and decaying; governance queue < 14 days.
  • Red: Any integrity regression; auto-freeze writes; require PRaaS intervention.

6) Worked Vertical: Mineral Language System (as a domain plugged into ULCP)

6.1 Purpose

Unify mineral names, variants, translations, industrial codes, and cultural/etymological traces; anchor to specimens and assays; publish to energy, manufacturing, finance, and media stacks.

6.2 Token Schema (adds to core)

"token": {
  "value": "Cobaltite",
  "kind": "mineral",
  "governedBy": "IMA-CNMNC",
  "language": "en",
  "etymology": "from German 'Kobold', goblin",
  "variants": [{"form":"Cobaltita","locale":"es"}],
  "composition": {"formula":"CoAsS"},
  "properties": {"system":"Isometric","hardness_Mohs":5.5}
}

6.3 Anchors

  • Specimen anchors: museum/herbarium/lab catalog IDs; microprobe/assay DOIs
  • Digital anchors: IMA CNMNC entries; Mindat/IMA URIs
  • Industrial anchors: HS codes; ISO material numbers; GS1 trade items (if traded)

6.4 Governance & Registries

  • Governance: IMA CNMNC (naming/priorities) → PRaaS opinions captured
  • Registries: IMA list, Mindat, Crossref DOIs for datasets; company asset ledgers for stockpiles

6.5 Cross-Sector Links

  • Energy: materials taxonomy → battery cathode mapping → compliance trails
  • Manufacturing: batch lineage → counterfeit prevention (EPCIS)
  • Finance/Insurance: exposure to strategic mineral supply → ESG overlays
  • Media/Publishing: registry-backed glossary; pronunciations & translations via TLaaS

6.6 KPIs

  • mineral_concordance_rate, assay_anchor_completeness, alias_collapse_latency, supply_lineage_coverage

7) Implementation Roadmap (phased, battle-tested)

  1. Bootstrap (Weeks 0–4)
    • Stand up NaaS/IDaaS/OaaS with the core JSON-LD context.
    • Load seed vocabularies + external registry resolvers.
    • Ship GET /ucls/resolve and GET /ucls/graph/search.
  2. Anchor & Validate (Weeks 5–8)
    • Wire AaaS + ValaaS; enforce SHACL; enable ProvAaaS trails.
    • Publish policy packs for top 3 sectors (your call: Healthcare, Energy, AI).
  3. Govern & Version (Weeks 9–12)
    • PRaaS/GaaS ballots/opinions; VaaS immutable releases; drift monitoring.
    • TLaaS for top locales; phoneme/morpheme engines.
  4. Interoperate & Analyze (Weeks 13–16)
    • InteropaaS adapters (FHIR, GBIF, EPCIS, XBRL, OPC UA/PDS4 as needed).
    • AnaaS quality dashboards; VizaaS sector maps/trees.
  5. Scale & Certify (Ongoing)
    • ACaaS VCs; throughput SLOs; chaos drills for registry outages.
    • Expand to remaining sectors; roll out mineral vertical as exemplar.

8) Logos Codex & Elemenomics (recursive hooks)

  • Symbolic layer: each token carries a harmonic signature (frequency ID linked to class/role), enabling resonance-based retrieval and mnemonic mapping.
  • Elemental layer: compounds/minerals/biochem entities map to Elemenomics nodes (element counts, valence patterns, energy roles).
  • Ethics/policy: GaaS embeds virtue constraints—explicit human-centric guardrails—with justifications preserved in ProvAaaS.

(A little tradition for the road: name things well, and they behave. We’re just making that ancient craft programmable.)