Electrical Engineering Domain Ontology

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

flow "ElectricalEngineeringDomainOntology" v1.0 {
  ontology:
    id: "electrical-engineering-domain-ontology"
    parent: "engineering-domains"
    purpose: "Represent electrical systems, components, circuits, measurements, energy conversion, controls, protection and evidence-backed engineering relationships."

  types:
    ElectricalSystem: {id: string, name: string, function: string, rated_voltage: Quantity?, provenance: string}
    Component: {id: string, kind: enum[resistor, capacitor, inductor, transformer, generator, motor, converter, switch, protection_device, conductor, sensor, other], rating: Quantity?, provenance: string}
    Circuit: {id: string, topology: string, supply_type: enum[AC, DC, mixed], provenance: string}
    Node: {id: string, circuit_id: string}
    Connection: {id: string, from_node: string, to_node: string, component_id: string?}
    Quantity: {value: number, unit: string, uncertainty: number?, reference_conditions: string?}
    Measurement: {id: string, quantity: Quantity, instrument: string, timestamp: datetime?, calibration_reference: string?, provenance: string}
    Requirement: {id: string, statement: string, criterion: string, provenance: string}
    Test: {id: string, method: string, outcome: enum[pass, fail, inconclusive], evidence: string[]}
    Relationship: {id: string, subject: string, predicate: string, object: string, context: string?, confidence: number, evidence: string[]}

  predicates:
    contains(system: ElectricalSystem, component: Component)
    belongs_to(circuit: Circuit, system: ElectricalSystem)
    connects(connection: Connection, node: Node)
    supplies(source: Component, load: Component)
    converts_energy(component: Component, input_form: string, output_form: string)
    controls(controller: Component, target: Component)
    protects(device: Component, circuit: Circuit)
    measured_by(subject: string, measurement: Measurement)
    satisfies(subject: string, requirement: Requirement)
    verified_by(requirement: Requirement, test: Test)
    depends_on(a: string, b: string)

  constraints:
    - "Every relationship endpoint must resolve to a declared, type-compatible entity."
    - "Confidence values must be within [0, 1]."
    - "Electrical quantities require units; compare only dimensionally compatible values."
    - "Voltage and current must specify AC/DC conventions, reference direction and RMS/peak interpretation when relevant."
    - "Electrical connections must be resolved within an identified circuit topology."
    - "Do not infer electrical safety or regulatory compliance from nominal component ratings alone."
    - "Do not infer causal control from mere connectivity or temporal association."
    - "Record operating conditions and uncertainty for measurements and calculated results."

  inference:
    rule component_membership:
      if contains(s,c) and belongs_to(k,s) and component_in_circuit(c,k)
      then associated_with(c,k)
      confidence: "retain source evidence; membership alone does not prove connectivity"
    rule ohms_law:
      if verified_resistive_element(c) and known_voltage(c,V) and known_resistance(c,R) and R > 0 and compatible_units(V,R)
      then calculated_current(c,V/R)
      confidence: "conditional on model validity, operating conditions and measurement uncertainty"
    rule power_relation:
      if known_voltage(c,V) and known_current(c,I) and dc_steady_state(c)
      then calculated_power(c,V*I)
      confidence: "retain sign convention and propagated uncertainty"
    rule requirement_evidence:
      if verified_by(r,t) and outcome(t) == pass and valid(t)
      then evidence_for_satisfaction(r,t)
      confidence: "test scope and acceptance criteria dependent"

  SEMANTIC_EQUIVALENCE:
    - "Normalise component classes and electrical quantities to versioned engineering vocabularies."
    - "Distinguish exact identity, functional similarity, replacement compatibility and aliases."
    - "Preserve units, operating conditions, circuit context and standard versions."

  CONFIDENCE:
    range: [0,1]
    factors: [measurement_uncertainty, calibration, source_reliability, model_assumptions, test_coverage, temporal_validity]
    policy: "Do not increase confidence solely by chaining dependent evidence or repeating measurements."

  VALIDATION:
    - "Check type constraints, identifier resolution and relationship cardinality."
    - "Validate dimensional consistency and measurement uncertainty."
    - "Check circuit connectivity and conservation laws only under declared modelling assumptions."
    - "Flag contradictory ratings, incompatible supply types and unverified compliance claims."
    - "Preserve unresolved evidence conflicts and alternative models."

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

  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 relationships"
    outputs: [entity_links, circuit_relationships, measurement_annotations, inferred_edges, requirement_traces, provenance_records]
    safeguards: [preserve_units, retain_uncertainty, no_unsupported_safety_claims, no_unverified_compliance_assertions]
}

END FLOW ALGEBRA