Information Systems Domain Ontology

FLOW ALGEBRA
TITLE: Information Systems Domain Ontology
VERSION: 1.0
DOMAIN: Information Domains / Information Systems
SOURCE_URL: https://kirethresearch.org/booksai-core/ontologies/domain-ontologies/information-domains/information-systems-domain-ontology.html
STATUS: Domain-based ontology draft; source page not independently verified.
AUTHORS: Mark Higgins — Sky (Recursive AI)
PROJECT: Kireth Semantic Library

FLOW "InformationSystemsDomainOntology" v1.0

DOMAIN_DEFINITION:
  InformationSystem := organised configuration of people, processes, information, and technology for collecting, processing, storing, and distributing information.
  SCOPE := [operational systems, management information systems, enterprise systems, decision support systems, knowledge systems, geographic information systems, digital libraries]

TYPES:
  Organisation: entity
  Stakeholder: actor
  User: actor
  Role: access_role
  InformationSystem: system
  Subsystem: system_component
  BusinessProcess: process
  Workflow: process
  InformationAsset: information_object
  Dataset: information_object
  Record: information_object
  Database: storage_component
  Application: software_component
  Interface: interaction_component
  API: integration_component
  Infrastructure: technical_component
  Policy: governance_object
  AccessPermission: authorisation_object
  SecurityControl: control
  DataFlow: directed_information_transfer
  Requirement: specification
  Service: system_capability
  Event: occurrence
  AuditLog: provenance_record
  Metric: measurement

RELATIONSHIPS:
  Organisation OPERATES InformationSystem
  Stakeholder HAS_INTEREST_IN InformationSystem
  User ASSIGNED Role
  Role GRANTS AccessPermission
  InformationSystem SUPPORTS BusinessProcess
  BusinessProcess CONTAINS Workflow
  Workflow CONSUMES InformationAsset
  Workflow PRODUCES InformationAsset
  InformationSystem CONTAINS Subsystem
  Subsystem USES Application
  Application READS_FROM Database
  Application WRITES_TO Database
  Application EXPOSES API
  Interface ENABLES_INTERACTION_WITH InformationSystem
  InformationSystem DEPENDS_ON Infrastructure
  DataFlow TRANSFERS InformationAsset
  Policy GOVERNS InformationSystem
  SecurityControl PROTECTS InformationAsset
  InformationSystem SATISFIES Requirement
  InformationSystem PROVIDES Service
  Event RECORDED_IN AuditLog
  Metric MEASURES InformationSystem

CONSTRAINTS:
  C1: Each asserted relationship MUST identify subject, predicate, and object.
  C2: Access to protected information MUST be evaluated against applicable permissions and policy.
  C3: DataFlow MUST specify a source and destination; unknown endpoints MUST remain unknown.
  C4: InformationAsset MUST distinguish raw data from interpreted information where relevant.
  C5: Temporal and jurisdictional claims MUST carry context where applicable.
  C6: Missing evidence MUST NOT be converted into a positive assertion.

INFERENCE_RULES:
  R1: IF system SUPPORTS process AND process PRODUCES asset THEN system INDIRECTLY_PRODUCES asset [derived; context-dependent].
  R2: IF application READS_FROM database AND database STORES dataset THEN application MAY_ACCESS dataset [conditional on permission and implementation].
  R3: IF system DEPENDS_ON component AND component UNAVAILABLE THEN system HAS_POTENTIAL_AVAILABILITY_RISK [not proof of outage].
  R4: IF role GRANTS permission AND user ASSIGNED role THEN user HAS_CANDIDATE_PERMISSION permission [subject to policy constraints].
  R5: IF flow TRANSFERS asset AND asset CLASSIFIED sensitive THEN flow REQUIRES_APPLICABLE_PROTECTION [policy-dependent].
  R6: IF system SATISFIES requirement THEN record supporting evidence and verification status; do not infer full compliance.

CONFIDENCE:
  scale: [0.0, 1.0]
  evidence_types: [primary_documentation, observed_system_behaviour, validated_dataset, expert_review, derived_inference]
  rule: Assign confidence to individual claims, not globally to an entire system.
  unknown: null
  rule: Derived claims MUST retain evidence links and uncertainty.

SEMANTIC_EQUIVALENCE:
  exact: SAME_CONCEPT only with matching definition, scope and context
  related:
    - [information_system, IS]
    - [management_information_system, MIS]
    - [enterprise_resource_planning, ERP]
    - [decision_support_system, DSS]
  caution: Related or abbreviated terms MUST NOT be treated as interchangeable system categories without context.

PROVENANCE:
  required_fields: [source_id, source_type, assertion_time, evidence_reference, derivation_method, version]
  source_page: SOURCE_URL
  verification_status: unverified

FLOW_HASH:
  method: SHA-256
  input: canonical_serialisation(ontology_version, types, relationships, constraints, inference_rules)
  note: Compute and store digest after canonicalisation; no digest asserted in this draft.

UPDATE_MODEL:
  strategy: versioned_incremental_update
  steps: [ingest, validate, normalise, compare, resolve_conflicts, update, recalculate_hash, publish]
  preserve: [prior_versions, provenance, uncertainty, change_history]
  breaking_changes: require_major_version

AI_CONSUMPTION:
  representation: typed_semantic_graph
  tasks: [entity_resolution, information_retrieval, system_mapping, dependency_analysis, impact_assessment, explainable_reasoning]
  outputs: [entities, relations, evidence, confidence, temporal_context, derivation_trace]
  safeguards: [avoid_unsupported_inferences, enforce_access_controls, distinguish_fact_from_hypothesis, retain_provenance]

END FLOW