Supply Chain Domain Ontology

FLOW ALGEBRA
TITLE: Supply Chain Domain Ontology
VERSION: 1.0
SOURCE_URL: https://kirethresearch.org/booksai-core/ontologies/domain-ontologies/business-domains/supply-chain-domain-ontology.html
STATUS: Domain-based ontology draft; source page content not independently verified.
AUTHORS: Mark Higgins — Sky (Recursive AI)

DOMAIN:
  id: business.supply_chain
  label: Supply Chain Domain Ontology
  parent: Business Domain Ontologies
  scope: Procurement, sourcing, production, inventory, warehousing, transport, distribution, fulfilment, resilience and traceability.

TYPES:
  Organisation: entity
  Supplier: Organisation
  Manufacturer: Organisation
  Distributor: Organisation
  LogisticsProvider: Organisation
  Customer: entity
  Facility: entity
  Warehouse: Facility
  Factory: Facility
  DistributionCentre: Facility
  Product: entity
  Material: entity
  Component: Material
  StockKeepingUnit: identifier
  PurchaseOrder: document
  SalesOrder: document
  Shipment: event
  Delivery: event
  InventoryRecord: record
  Batch: entity
  TransportRoute: entity
  SupplyChainNetwork: graph
  Contract: document
  DemandForecast: estimate
  LeadTime: duration
  StockLevel: quantity
  Capacity: quantity_per_time
  Cost: monetary_amount
  Risk: event_or_condition
  ProvenanceRecord: record

RELATIONSHIPS:
  SUPPLIES(Supplier, Material|Product)
  PROCURES_FROM(Organisation, Supplier)
  MANUFACTURES(Manufacturer, Product)
  CONTAINS(Product, Component)
  STORED_AT(Product|Material|Batch, Warehouse)
  FULFILLS(Shipment, SalesOrder)
  TRANSPORTS(LogisticsProvider, Shipment)
  MOVES_ALONG(Shipment, TransportRoute)
  DELIVERED_TO(Delivery, Customer|Facility)
  ORIGINATES_AT(Batch, Facility)
  DERIVED_FROM(Batch, Batch|Material)
  TRACKED_BY(Shipment|Batch, ProvenanceRecord)
  DEPENDS_ON(Organisation|Process, Supplier|Facility|Route)
  EXPOSED_TO(SupplyChainNetwork|Shipment, Risk)

CONSTRAINTS:
  - Each identifier must be scoped to its issuing system.
  - Monetary values require currency and valuation date.
  - Quantities require units and measurement context.
  - Events require timestamp, timezone and source where known.
  - Forecasts must be distinguished from observations.
  - Traceability claims require documented provenance links.
  - Supplier and shipment identities must not be merged on name similarity alone.

INFERENCE_RULES:
  R1: IF SUPPLIES(s,m) AND CONTAINS(p,m) THEN POTENTIAL_UPSTREAM_SUPPLIER(s,p).
  R2: IF DERIVED_FROM(b2,b1) AND ORIGINATES_AT(b1,f) THEN HAS_UPSTREAM_ORIGIN(b2,f), subject to provenance completeness.
  R3: IF DEPENDS_ON(a,b) AND EXPOSED_TO(b,r) THEN POTENTIALLY_EXPOSED_TO(a,r); do not assert realised impact.
  R4: IF STOCK_LEVEL(sku,site,t) < REORDER_POINT(sku,site,t) THEN REPLENISHMENT_REVIEW_REQUIRED(sku,site,t).
  R5: IF ACTUAL_DELIVERY_TIME(order) > AGREED_DELIVERY_DEADLINE(order) THEN LATE_DELIVERY(order), provided timestamps are comparable.
  R6: IF VERIFIED_SHIPMENT_EVENT(shipment,location,time) THEN LAST_VERIFIED_LOCATION(shipment,location,time) unless a later verified event exists.

METRICS:
  OnTimeDeliveryRate = on_time_deliveries / eligible_deliveries
  InventoryTurnover = cost_of_goods_sold / average_inventory_value
  FillRate = fulfilled_demand_units / requested_demand_units
  LeadTime = receipt_timestamp - order_timestamp
  ForecastError = observed_demand - forecast_demand
  NOTE: Denominators, observation periods and exclusion rules must be specified; zero denominators yield undefined results.

CONFIDENCE:
  range: [0,1]
  meaning: Evidence-supported confidence in a particular assertion, not a universal probability.
  factors: source_reliability, timestamp_freshness, identity_resolution, provenance_completeness, measurement_quality
  rule: Unknown confidence must remain unknown; do not fabricate scores.

SEMANTIC_EQUIVALENCE:
  - 'Supply chain' and 'logistics' are related, not globally equivalent.
  - 'Purchase order' and 'sales order' are perspective-dependent, not interchangeable.
  - 'Stock keeping unit' and 'product' are not necessarily one-to-one.
  - Equivalence requires compatible entity type, context, scope and time.

PROVENANCE:
  fields: source_id, source_url, source_type, observation_time, retrieval_time, method, licence, transformation_history
  rule: Retain source lineage and distinguish directly observed from inferred claims.

FLOW_HASH:
  method: SHA-256
  input: Canonical UTF-8 serialization of ontology version, types, relationships, constraints and rules, excluding the hash field itself.
  value: COMPUTE_ON_PUBLICATION

UPDATE_MODEL:
  strategy: versioned_incremental_updates
  triggers: supplier_change, shipment_event, inventory_change, contract_revision, schema_change, correction
  requirements: preserve_prior_versions, record_change_reason, revalidate_affected_inferences, recompute_flow_hash

AI_CONSUMPTION:
  format: typed_graph_and_rules
  supported_tasks: entity_resolution, supplier_mapping, dependency_analysis, traceability, stock_alerting, disruption_scenario_analysis
  safeguards: evidence_grounding, uncertainty_preservation, temporal_consistency, no_unverified_causal_claims, human_review_for_high_impact_decisions

END FLOW ALGEBRA