Cross-Domain Relationship Ontology

FLOW ALGEBRA
TITLE: Cross-Domain Relationship Ontology
DOMAIN: Knowledge Graph Relationships / Cross-Domain Semantics
SOURCE: https://kirethresearch.org/booksai-core/ontologies/relationship-ontologies/knowledge-graph-relationships/cross-domain-relationship-ontology.html
VERSION: 1.0
AUTHORS: Mark Anthony Higgins — Sky (Recursive AI)
STATUS: Companion formalisation; source-page specification not independently verified.

flow "CrossDomainRelationshipOntology" v1.0 {
  ontology:
    id: "cross-domain-relationship-ontology"
    parent: "knowledge-graph-relationships"
    purpose: "Represent evidence-backed relationships between entities, concepts and assertions belonging to distinct knowledge domains without collapsing domain-specific meaning."

  types:
    Domain: {id: string, name: string, ontology_iri: string?, version: string?}
    Entity: {id: string, domain_id: string, class_iri: string, label: string?}
    Concept: {id: string, domain_id: string, definition: string?, scope: string?}
    Mapping: {id: string, source_id: string, target_id: string, relation: enum[exact_match, close_match, broader_match, narrower_match, related_match, transforms_to, depends_on], context: string?, confidence: number, evidence: string[]}
    Assertion: {id: string, subject_id: string, predicate_iri: string, object_id: string, graph_id: string?, provenance: string}
    Evidence: {id: string, source: string, method: string?, timestamp: datetime?, quality: number?}

  predicates:
    belongs_to(entity: Entity, domain: Domain)
    maps_to(source: Entity|Concept, target: Entity|Concept, mapping: Mapping)
    related_across_domains(source: Entity|Concept, target: Entity|Concept)
    supported_by(mapping: Mapping, evidence: Evidence)
    uses_ontology(domain: Domain, ontology_iri: string)
    transforms_to(source: Entity|Concept, target: Entity|Concept)

  constraints:
    - "Every cross-domain link must identify both source and target domains."
    - "Mapping endpoints must resolve to typed entities or concepts."
    - "Confidence values must lie within [0,1]."
    - "Do not equate exact_match, close_match, related_match or identity."
    - "Do not assume a cross-domain mapping is symmetric or transitive unless its specific relation semantics permit it."
    - "Preserve units, definitions, scope, context, provenance and ontology versions."
    - "Cross-domain causation requires independent causal evidence; association alone is insufficient."
    - "Resolve ontology conflicts explicitly rather than silently overwriting assertions."

  inference:
    rule cross_domain_link:
      if maps_to(a,b,m) and valid(m) and domain(a) != domain(b)
      then related_across_domains(a,b)
      confidence: "bounded by mapping confidence and supporting evidence"
    rule validated_equivalence:
      if maps_to(a,b,m) and m.relation == exact_match and compatible_definitions(a,b) and valid(m)
      then candidate_semantic_equivalence(a,b)
      confidence: "requires independent review before asserting identity"
    rule chained_mapping:
      if maps_to(a,b,m1) and maps_to(b,c,m2) and composition_permitted(m1.relation,m2.relation)
      then candidate_mapping(a,c)
      confidence: "re-evaluate against endpoint semantics; never increase confidence by chaining alone"

  SEMANTIC_EQUIVALENCE:
    - "Normalise identifiers using versioned ontology registries and canonical IRIs."
    - "Differentiate exact semantic correspondence from approximate alignment and shared labels."
    - "Require compatible definitions and contexts before accepting equivalence."
    - "Retain original source terminology and domain-specific distinctions."

  CONFIDENCE:
    range: [0,1]
    factors: [source_reliability, semantic_compatibility, contextual_fit, ontology_version, evidence_quality, independent_validation]
    policy: "Preserve uncertainty; inferred mappings must not be assigned greater confidence solely because they are chained."

  VALIDATION:
    - "Check entity resolution, domain membership, property compatibility and mapping direction."
    - "Validate identifiers, ontology versions, provenance and confidence bounds."
    - "Flag ambiguous labels, conflicting mappings and incompatible domain assumptions."
    - "Keep competing mappings where available evidence is inconclusive."

  FLOW_HASH:
    algorithm: "SHA-256"
    input: "canonicalised ontology version, domains, mappings, assertions, inference rules and provenance"
    note: "Compute hash at execution; no hash value is claimed here."

  UPDATE_MODEL:
    strategy: "versioned, provenance-preserving incremental alignment"
    steps: [ingest, resolve_domains, normalise_identifiers, propose_mappings, validate, reconcile_conflicts, recompute_inferences, publish]
    rollback: true

  AI_CONSUMPTION:
    representation: "typed, provenance-aware cross-domain knowledge graph"
    outputs: [cross_domain_edges, mapping_candidates, equivalence_annotations, confidence_scores, inference_traces, provenance_records]
    safeguards: [no_unsupported_identity_merges, no_unjustified_transitivity, preserve_domain_context, retain_uncertainty, respect_ontology_versions]
}

END FLOW ALGEBRA