Mechanical Engineering Domain Ontology

FLOW ALGEBRA
TITLE: Mechanical Engineering Domain Ontology
DOMAIN: Domain Ontologies / Engineering Domains / Mechanical Engineering
SOURCE: https://kirethresearch.org/booksai-core/ontologies/domain-ontologies/engineering-domains/mechanical-engineering-domain-ontology.html
VERSION: 1.0
AUTHORS: Mark Anthony Higgins — Sky (Recursive AI)
STATUS: Companion formalisation; source-page specification not independently verified.

flow "MechanicalEngineeringDomainOntology" v1.0 {
  ontology:
    id: "mechanical-engineering-domain-ontology"
    parent: "engineering-domains"
    purpose: "Represent mechanical systems, components, loads, motion, energy, materials, analysis, testing and engineering evidence with explicit physical constraints."

  types:
    MechanicalSystem: {id: string, name: string, function: string, operating_context: string?}
    Component: {id: string, name: string, component_type: string, material_id: string?}
    Material: {id: string, designation: string, properties: map<string, Quantity>}
    Load: {id: string, kind: enum[force, torque, pressure, thermal, dynamic, other], magnitude: Quantity, direction: string?}
    Motion: {id: string, kind: enum[translation, rotation, vibration, deformation], measurement: Quantity?}
    EnergyTransfer: {id: string, kind: enum[work, heat, fluid_power, other], quantity: Quantity}
    Requirement: {id: string, statement: string, acceptance_criterion: string, provenance: string}
    Analysis: {id: string, method: string, assumptions: string[], model_version: string, provenance: string}
    Test: {id: string, procedure: string, conditions: string, result: string?, provenance: string}
    Quantity: {value: number, unit: string, uncertainty: number?, reference_frame: string?, timestamp: datetime?}
    Relationship: {id: string, subject: string, predicate: string, object: string, confidence: number, evidence: string[]}

  predicates:
    part_of(component: Component, system: MechanicalSystem)
    connected_to(a: Component, b: Component)
    made_of(component: Component, material: Material)
    subjected_to(component: Component, load: Load)
    exhibits_motion(component: Component, motion: Motion)
    transfers_energy(source: Component, target: Component, transfer: EnergyTransfer)
    satisfies(system: MechanicalSystem, requirement: Requirement)
    analysed_by(system: MechanicalSystem, analysis: Analysis)
    verified_by(requirement: Requirement, test: Test)
    depends_on(a: Component, b: Component)

  constraints:
    - "All relationship endpoints must resolve to compatible typed entities."
    - "Confidence must be within [0,1]."
    - "Physical quantities require explicit units and dimensional consistency."
    - "Reference frames, operating conditions and uncertainty must be retained when relevant."
    - "Component membership does not imply functional dependency or causal control."
    - "Verification claims require applicable acceptance criteria and recorded evidence."
    - "Simulation outputs must be distinguished from experimental measurements."
    - "Do not infer safety, reliability or compliance solely from nominal calculations."

  inference:
    rule component_membership:
      if part_of(c,s) and valid(c) and valid(s)
      then member_of_system(c,s)
      confidence: "retain supporting provenance"
    rule mechanical_dependency:
      if depends_on(a,b) and depends_on(b,c) and dependency_chain_valid(a,b,c)
      then indirectly_depends_on(a,c)
      confidence: "do not imply direct physical connection"
    rule requirement_verification:
      if verified_by(r,t) and passed(t) and conditions_match(t,r)
      then evidence_for_satisfaction(r,t)
      confidence: "bounded by test quality and coverage"

  SEMANTIC_EQUIVALENCE:
    - "Normalise engineering terminology against versioned domain vocabularies."
    - "Distinguish identical components from interchangeable or functionally similar components."
    - "Preserve units, tolerances, reference frames and operating context in mappings."

  CONFIDENCE:
    range: [0,1]
    factors: [measurement_uncertainty, evidence_quality, model_validity, operating_conditions, independent_verification]
    policy: "Never increase confidence merely through inference chaining."

  VALIDATION:
    - "Validate identifiers, endpoint types and relationship direction."
    - "Check dimensional consistency and physically plausible ranges."
    - "Verify assumptions, test conditions, material properties and traceability."
    - "Flag conflicting evidence, unverified requirements and unsupported performance claims."

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

  UPDATE_MODEL:
    strategy: "versioned, provenance-preserving incremental update"
    steps: [ingest, normalise, validate, compare, reconcile, recompute_inferences, publish]
    rollback: true

  AI_CONSUMPTION:
    representation: "typed engineering knowledge graph with evidence-backed relations"
    outputs: [entity_links, component_relationships, requirement_traceability, uncertainty_annotations, inferred_edges, provenance_records]
    safeguards: [preserve_units, distinguish_simulation_from_measurement, no_unverified_safety_claims, maintain_traceability]
}

END FLOW ALGEBRA