Business Domain Ontology

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

flow "BusinessDomainOntology" v1.0

DOMAIN:
  id: business_domain_ontology
  label: Business Domain Ontology
  parent: Business Domains
  scope: Organisations, operations, finance, markets, governance, strategy and business processes.

ENTITY_TYPES:
  - Organisation: {attributes: [identifier, name, legal_form, sector, jurisdiction]}
  - BusinessUnit: {attributes: [identifier, name, function]}
  - Stakeholder: {attributes: [identifier, role, interests]}
  - Employee: {attributes: [identifier, role, employment_status]}
  - Customer: {attributes: [identifier, segment]}
  - Supplier: {attributes: [identifier, supplied_category]}
  - Product: {attributes: [identifier, category, price, currency]}
  - Service: {attributes: [identifier, scope, price, currency]}
  - Transaction: {attributes: [identifier, timestamp, amount, currency, status]}
  - Contract: {attributes: [identifier, parties, effective_date, expiry_date, terms]}
  - BusinessProcess: {attributes: [identifier, inputs, outputs, owner]}
  - Resource: {attributes: [identifier, type, capacity]}
  - Asset: {attributes: [identifier, type, valuation_date, value, currency]}
  - Liability: {attributes: [identifier, amount, currency, due_date]}
  - Market: {attributes: [identifier, geography, sector]}
  - Strategy: {attributes: [identifier, objective, horizon]}
  - PerformanceIndicator: {attributes: [identifier, unit, period, definition]}
  - Regulation: {attributes: [identifier, jurisdiction, effective_date]}
  - Risk: {attributes: [identifier, likelihood, impact, assessment_date]}

RELATIONSHIP_TYPES:
  - Organisation HAS_UNIT BusinessUnit
  - Organisation EMPLOYS Employee
  - Organisation SERVES Customer
  - Organisation CONTRACTS_WITH Supplier
  - Organisation OFFERS Product
  - Organisation OFFERS Service
  - Organisation OPERATES_IN Market
  - Organisation OWNS Asset
  - Organisation OWES Liability
  - Stakeholder HAS_INTEREST_IN Organisation
  - BusinessUnit EXECUTES BusinessProcess
  - BusinessProcess USES Resource
  - BusinessProcess PRODUCES Product
  - Transaction INVOLVES Organisation
  - Transaction GOVERNED_BY Contract
  - Strategy SETS_OBJECTIVE_FOR Organisation
  - PerformanceIndicator MEASURES BusinessProcess
  - Regulation APPLIES_TO Organisation
  - Risk THREATENS BusinessProcess

CONSTRAINTS:
  - Entity identifiers must be unique within their namespace.
  - Financial values require explicit currency and observation period where applicable.
  - Jurisdiction-sensitive claims require a jurisdiction and effective date.
  - Contractual relationships must not be inferred from commercial contact alone.
  - Correlation between indicators must not be interpreted as causation without evidence.
  - Personal information must be minimised and handled according to applicable law.

INFERENCE_RULES:
  - id: R1
    when: Organisation OFFERS Product AND Product TARGETS Market
    then: Organisation MAY_SERVE Market
    confidence: conditional
  - id: R2
    when: BusinessProcess USES Resource AND Resource IS_UNAVAILABLE
    then: BusinessProcess HAS_POTENTIAL_DISRUPTION
    confidence: conditional
  - id: R3
    when: Regulation APPLIES_TO Organisation AND Regulation IS_EFFECTIVE
    then: Organisation HAS_COMPLIANCE_OBLIGATION
    confidence: requires_verified_scope
  - id: R4
    when: PerformanceIndicator MEASURES BusinessProcess AND comparable_time_series_exists
    then: BusinessProcess HAS_MEASURABLE_TREND
    confidence: depends_on_data_quality
  - id: R5
    when: Contract BINDS Organisation AND Contract HAS_VALID_TERM
    then: Organisation HAS_CONTRACTUAL_RELATIONSHIP
    confidence: requires_documentary_evidence

CONFIDENCE:
  scale: [0.0, 1.0]
  dimensions: [source_reliability, evidence_strength, temporal_validity, semantic_fit]
  rule: Do not assign numeric certainty without supporting evidence or calibration.

SEMANTIC_EQUIVALENCE:
  exact: [Organisation|Organization, Customer|Client_when_contextually_identical]
  related_not_identical: [Revenue|Profit, Supplier|Partner, Asset|Resource, Strategy|BusinessPlan]
  rule: Resolve aliases by jurisdiction, sector, definition and context; never equate related terms automatically.

PROVENANCE:
  required_fields: [source_uri, source_type, extraction_or_assertion_date, assertion_method]
  distinguish: [source_fact, model_inference, human_interpretation]
  source_uri: https://kirethresearch.org/booksai-core/ontologies/domain-ontologies/business-domains/business-domain-ontology.html
  source_verification: not_performed

FLOW_HASH:
  algorithm: SHA-256
  input: canonical_serialisation_of_ontology_version_and_content
  generation: calculate_at_publication; no fabricated hash

UPDATE_MODEL:
  versioning: semantic_versioning
  triggers: [new_evidence, regulatory_change, revised_definition, relationship_change]
  process: [validate_source, reconcile_entities, check_constraints, review_inferences, increment_version, recalculate_hash, record_changelog]

AI_CONSUMPTION:
  format: UTF-8 plain text
  use_cases: [semantic_search, entity_linking, knowledge_graphs, retrieval_augmented_generation, constrained_reasoning]
  safeguards: [preserve_provenance, label_inference, respect_temporal_scope, avoid_unsupported_claims]
  output_contract: Return typed entities and relations with provenance, confidence and unresolved ambiguities.

END FLOW ALGEBRA