Engineering Domain Ontology

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

flow "EngineeringDomainOntology" v1.0 {
  ontology:
    id: "engineering-domain-ontology"
    parent: "engineering-domains"
    purpose: "Represent engineering systems, requirements, designs, components, processes, tests and their evidence-backed relationships."

  types:
    EngineeringSystem: {id: string, name: string, discipline: string, lifecycle_state: string}
    Component: {id: string, type: string, system_id: string, revision: string?}
    Requirement: {id: string, statement: string, priority: string?, verification_method: string?}
    Design: {id: string, revision: string, specification: string, provenance: string}
    Interface: {id: string, kind: string, protocol: string?, constraints: string[]}
    Process: {id: string, kind: string, inputs: string[], outputs: string[]}
    Measurement: {id: string, quantity: number, unit: string, uncertainty: number?, timestamp: datetime?, provenance: string}
    Test: {id: string, procedure: string, result: enum[pass, fail, inconclusive], evidence: string[]}
    Relationship: {id: string, subject: string, predicate: string, object: string, context: string?, confidence: number, evidence: string[]}

  predicates:
    part_of(component: Component, system: EngineeringSystem)
    connects_to(a: Component, b: Component, interface: Interface)
    depends_on(a: string, b: string)
    satisfies(design: Design, requirement: Requirement)
    verified_by(requirement: Requirement, test: Test)
    measured_by(entity: string, measurement: Measurement)
    transforms(process: Process, input: string, output: string)
    supersedes(new_design: Design, old_design: Design)

  constraints:
    - "All relationship endpoints must resolve to typed entities."
    - "Confidence must lie within [0, 1]."
    - "Measurements must specify units and uncertainty when available."
    - "Design satisfaction must not imply verified compliance without supporting test evidence."
    - "Dependency and connectivity are not automatically transitive."
    - "Preserve component and design revisions in relationship context."
    - "A failed test cannot be silently converted to a successful verification."
    - "Engineering decisions must preserve applicable safety constraints and evidence."

  inference:
    rule system_membership:
      if part_of(c,s) and valid(c) and valid(s)
      then system_contains(s,c)
      confidence: "retain source evidence"
    rule verification_status:
      if verified_by(r,t) and t.result == pass and valid(t)
      then evidence_supports_requirement(t,r)
      confidence: "bounded by test applicability and quality"
    rule design_lineage:
      if supersedes(d2,d1) and supersedes(d3,d2)
      then design_ancestor(d1,d3)
      confidence: "preserve revision provenance"
    rule dependency_impact:
      if depends_on(a,b) and changed(b)
      then requires_impact_assessment(a)
      confidence: "impact is a review obligation, not a proven failure"

  SEMANTIC_EQUIVALENCE:
    - "Map engineering terminology using discipline-specific, versioned vocabularies."
    - "Distinguish same identity, equivalent function, interchangeable component and similar design."
    - "Preserve units, operating conditions, tolerances and revision scope."

  CONFIDENCE:
    range: [0,1]
    factors: [measurement_quality, test_coverage, source_reliability, design_revision, operating_context, independent_replication]
    policy: "Do not inflate confidence through repeated or circular inference."

  VALIDATION:
    - "Check entity types, relationship domains and ranges, and referential integrity."
    - "Validate measurement units, uncertainty and operating context."
    - "Flag unmet requirements, contradictory test results and unresolved dependencies."
    - "Distinguish proposed, simulated, tested and deployed engineering states."

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

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

  AI_CONSUMPTION:
    representation: "typed engineering knowledge graph with evidence-backed relationships"
    outputs: [system_maps, requirement_links, dependency_edges, verification_records, uncertainty_annotations, provenance_records]
    safeguards: [no_unverified_compliance_claims, preserve_design_revisions, preserve_units_and_tolerances, flag_safety_critical_uncertainty]
}

END FLOW ALGEBRA