Civil Engineering Domain Ontology

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

flow "CivilEngineeringDomainOntology" v1.0 {
  ontology:
    id: "civil-engineering-domain-ontology"
    parent: "engineering-domains"
    purpose: "Represent civil infrastructure, engineering requirements, design assumptions, construction activities, inspections and evidence-backed performance relationships."

  types:
    InfrastructureAsset: {id: string, class: enum[bridge, building, road, railway, tunnel, dam, water_network, drainage_system, foundation, other], lifecycle_state: string}
    Component: {id: string, asset_id: string, kind: string, material_id: string?}
    Material: {id: string, specification: string, properties: map[string, Quantity]}
    Site: {id: string, coordinate_reference_system: string?, ground_conditions: string?, provenance: string}
    Requirement: {id: string, description: string, criterion: string, standard_ref: string?}
    LoadCase: {id: string, kind: string, magnitude: Quantity, combination_ref: string?}
    Quantity: {value: number, unit: string, uncertainty: number?, reference_frame: string?}
    DesignModel: {id: string, version: string, assumptions: string[], provenance: string}
    Activity: {id: string, kind: enum[survey, design, construction, inspection, maintenance, repair, other], timestamp: datetime?, actor: string?}
    Evidence: {id: string, source: string, timestamp: datetime?, method: string, uncertainty: number?}
    Relationship: {id: string, subject: string, predicate: string, object: string, confidence: number, evidence: string[], context: string?}

  predicates:
    component_of(component: Component, asset: InfrastructureAsset)
    uses_material(component: Component, material: Material)
    located_at(asset: InfrastructureAsset, site: Site)
    subject_to(asset: InfrastructureAsset, load: LoadCase)
    satisfies(asset: InfrastructureAsset, requirement: Requirement)
    assessed_by(asset: InfrastructureAsset, model: DesignModel)
    supported_by(assertion: Relationship, evidence: Evidence)
    depends_on(activity_a: Activity, activity_b: Activity)
    affects(activity: Activity, asset: InfrastructureAsset)

  constraints:
    - "All relationship endpoints must resolve to typed entities."
    - "Confidence values must lie within [0, 1]."
    - "Physical quantities must include units and relevant reference frames."
    - "Design compliance requires an explicit criterion, applicable standard version and evidence."
    - "A simulation result must not be treated as measured performance without independent validation."
    - "Do not infer structural safety solely from component membership or material classification."
    - "Causal conclusions require adequate evidence; correlation alone is insufficient."
    - "Distinguish proposed, designed, constructed, inspected and operational states."

  inference:
    rule asset_component:
      if component_of(c,a) and uses_material(c,m)
      then asset_has_material_component(a,m,c)
      confidence: "derived; preserve component scope"
    rule prerequisite_chain:
      if depends_on(a,b) and depends_on(b,c) and compatible_workflow(a,b,c)
      then indirectly_depends_on(a,c)
      confidence: "retain source dependencies"
    rule verified_requirement:
      if assessed_by(a,m) and checks(m,r) and valid(m) and evidence_confirms(a,r)
      then candidate_satisfaction(a,r)
      confidence: "conditional on model validity and evidence"

  SEMANTIC_EQUIVALENCE:
    - "Normalise civil engineering terms against versioned standards and controlled vocabularies."
    - "Distinguish identical assets from equivalent designs or functionally similar components."
    - "Preserve units, geographic references, design codes and lifecycle context."

  CONFIDENCE:
    range: [0,1]
    factors: [measurement_uncertainty, inspection_quality, model_validity, source_reliability, standards_applicability, temporal_validity]
    policy: "Do not increase confidence merely by chaining inferences or repeating dependent evidence."

  VALIDATION:
    - "Check identifiers, type compatibility, units and referential integrity."
    - "Check design assumptions, load combinations, model versions and applicable standards."
    - "Flag contradictory measurements, outdated inspections and unresolved requirements."
    - "Retain uncertain or competing assessments with provenance."

  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 civil engineering knowledge graph with evidence-backed edges"
    outputs: [asset_links, component_relationships, requirement_traces, engineering_constraints, uncertainty_annotations, provenance_records]
    safeguards: [no_unverified_safety_claims, preserve_units_and_standards, distinguish_model_from_measurement, require_human_engineering_review]
}

END FLOW ALGEBRA