Construction Domain Ontology

FLOW ALGEBRA
Construction Domain Ontology v1.0
Kireth Semantic Library
Source: https://kirethresearch.org/booksai-core/ontologies/domain-ontologies/industry-domains/construction-domain-ontology.html
Status: Domain-based draft; source webpage content not independently verified.
Authors: Mark Higgins — Sky (Recursive AI)

flow "ConstructionDomainOntology" v1.0

DOMAIN:
  id: construction_domain_ontology
  parent: industry_domains
  scope: [construction_projects, built_assets, site_operations, building_materials, trades, procurement, safety, quality, compliance, handover]

ENTITY_TYPES:
  ConstructionProject: {fields: [project_id, name, location, scope, budget, schedule, status]}
  BuiltAsset: {fields: [asset_id, asset_type, location, design_life, status]}
  Building: {extends: BuiltAsset}
  InfrastructureAsset: {extends: BuiltAsset}
  Client: {fields: [party_id, organisation_name]}
  Contractor: {fields: [party_id, specialism, qualifications]}
  Subcontractor: {extends: Contractor}
  Designer: {fields: [party_id, discipline, professional_role]}
  ConstructionWorker: {fields: [worker_id, trade, competence, certification]}
  ConstructionSite: {fields: [site_id, location, access_controls, hazards]}
  WorkPackage: {fields: [package_id, scope, start_date, finish_date, status]}
  ConstructionActivity: {fields: [activity_id, method, duration, progress, status]}
  Material: {fields: [material_id, specification, quantity, unit, provenance]}
  Equipment: {fields: [equipment_id, type, inspection_status, availability]}
  DesignDocument: {fields: [document_id, revision, author, approval_status]}
  BuildingInformationModel: {fields: [model_id, revision, coordinate_reference, provenance]}
  Permit: {fields: [permit_id, issuing_authority, scope, validity_period]}
  Inspection: {fields: [inspection_id, inspector, date, result, evidence]}
  SafetyHazard: {fields: [hazard_id, likelihood, consequence, controls]}
  QualityDefect: {fields: [defect_id, severity, location, corrective_action, status]}
  ChangeOrder: {fields: [change_id, reason, cost_impact, schedule_impact, approval_status]}
  HandoverRecord: {fields: [record_id, asset_id, completion_date, documentation]}

RELATIONSHIP_TYPES:
  commissioned_by: ConstructionProject -> Client
  delivered_by: ConstructionProject -> Contractor
  designed_by: BuiltAsset -> Designer
  located_at: BuiltAsset|ConstructionActivity -> ConstructionSite
  decomposes_into: ConstructionProject -> WorkPackage
  contains_activity: WorkPackage -> ConstructionActivity
  precedes: ConstructionActivity -> ConstructionActivity
  depends_on: ConstructionActivity -> ConstructionActivity
  performed_by: ConstructionActivity -> Contractor|ConstructionWorker
  uses_material: ConstructionActivity -> Material
  uses_equipment: ConstructionActivity -> Equipment
  governed_by: ConstructionActivity -> Permit
  documented_by: BuiltAsset|ConstructionActivity -> DesignDocument|BuildingInformationModel
  inspected_by: ConstructionActivity|BuiltAsset -> Inspection
  exposes_hazard: ConstructionActivity -> SafetyHazard
  identifies_defect: Inspection -> QualityDefect
  changes_scope_of: ChangeOrder -> WorkPackage|ConstructionProject
  handed_over_as: BuiltAsset -> HandoverRecord

CONSTRAINTS:
  - Entity identifiers must be unique within their declared type.
  - All quantities must carry explicit units.
  - Schedule dependencies must not form an unapproved cycle.
  - A permit is valid only within its stated jurisdiction, scope and validity period.
  - Inspection results must be tied to dated evidence and the inspected revision.
  - Safety and compliance conclusions require applicable local rules and competent review.
  - Unknown, unverified and not_applicable are distinct states.

INFERENCE_RULES:
  R1: IF activity_A precedes activity_B AND activity_A is incomplete THEN flag activity_B as dependency_pending; do not assume delay without schedule evidence.
  R2: IF material specification differs from approved design THEN flag specification_mismatch for review.
  R3: IF permit validity has expired AND activity requires permit THEN flag authorisation_review_required.
  R4: IF inspection records a defect THEN create corrective_action_required linked to inspection evidence.
  R5: IF approved change_order affects critical-path activity THEN recompute schedule impact using a validated schedule model.
  R6: IF safety_hazard lacks verified controls THEN flag safety_review_required; do not infer work is safe.
  R7: IF handover documentation is incomplete THEN flag handover_readiness_unknown_or_incomplete.

CONFIDENCE:
  range: [0.0, 1.0]
  interpretation: epistemic_confidence_not_safety_certification
  required_evidence: [source, timestamp, method, scope]
  aggregation: avoid_unjustified_independence_assumptions

SEMANTIC_EQUIVALENCE:
  aliases:
    - [construction_project, building_project]
    - [work_package, package_of_work]
    - [building_information_model, BIM_model]
  rule: contextual_equivalence_only; preserve differences between construction, refurbishment, repair and maintenance.

PROVENANCE:
  required: [source_uri, author_or_organisation, observation_time, version, evidence_type]
  record_changes: true
  preserve_original_assertions: true

FLOW_HASH:
  algorithm: SHA-256
  input: canonical_serialisation_of_flow_definition
  computation: at_publication_time
  note: no hash value asserted until computed from final published bytes

UPDATE_MODEL:
  strategy: versioned_incremental_updates
  triggers: [design_revision, regulation_change, inspection_result, schedule_change, material_substitution, project_handover]
  validation: [schema_check, referential_integrity, provenance_check, conflict_review]
  conflict_policy: retain_history_and_escalate_unresolved_conflicts

AI_CONSUMPTION:
  formats: [plain_text_flow_algebra, structured_graph_mapping]
  functions: [entity_extraction, relation_mapping, dependency_analysis, evidence_based_retrieval, anomaly_flagging]
  guardrails: [do_not_invent_permits, do_not_certify_structural_safety, distinguish_plans_from_as_built, require_human_professional_review]
  output_fields: [entities, relationships, inferences, confidence, provenance, unresolved_questions]

END FLOW