Update Metadata Ontology

FLOW ALGEBRA

Ontology: Update Metadata Ontology
Domain: Metadata Ontologies > AI Semantic Library Metadata
Canonical URL: https://kirethresearch.org/booksai-core/ontologies/metadata-ontologies/ai-semantic-library-metadata/update-metadata-ontology.html
Authors: Mark Anthony Higgins — Sky (Recursive AI)

flow "UpdateMetadataOntology" v1.0

# ---------- DOMAIN ----------
domain:
  class: MetadataOntology
  category: AISemanticLibraryMetadata
  subject: UpdateMetadata
  purpose:
    - represent semantic updates, state transitions, triggers, affected resources, validation, versioning, FlowHash changes, and provenance
    - preserve previous, proposed, and resulting state, update reason, scope, dependencies, confidence, validity, and rollback context
    - support ontology evolution, Flow Algebra updates, knowledge-graph maintenance, semantic-library synchronisation, recursive updates, and machine reasoning
    - distinguish semantic updates from editorial changes, execution, replacement, deletion, and inferred change

# ---------- CORE ----------
entity UpdateMetadata:
  type: SemanticLibraryMetadata
  describes: SemanticUpdate
  may_include:
    - update_identifier
    - subject_identifier
    - subject_type
    - trigger
    - update_type
    - previous_state
    - proposed_state
    - resulting_state
    - affected_entities
    - affected_relationships
    - affected_rules
    - dependencies
    - validation
    - confidence
    - version_action
    - flow_hash_action
    - rollback
    - validity
    - provenance

entity SemanticUpdate:
  type: SemanticChangeProcess

entity UpdateIdentifier:
  type: PersistentIdentifier
  identifies: SemanticUpdate

relationships:
  UpdateMetadata -> DESCRIBES -> SemanticUpdate
  SemanticUpdate -> APPLIES_TO -> SemanticResource
  SemanticUpdate -> TRIGGERED_BY -> UpdateTrigger
  SemanticUpdate -> HAS_TYPE -> UpdateType
  SemanticUpdate -> TRANSITIONS_FROM -> PreviousSemanticState
  SemanticUpdate -> TRANSITIONS_TO -> ResultingSemanticState
  SemanticUpdate -> MAY_AFFECT -> SemanticEntity
  SemanticUpdate -> MAY_AFFECT -> SemanticRelationship
  SemanticUpdate -> MAY_AFFECT -> SemanticRule
  SemanticUpdate -> MAY_REQUIRE -> UpdateValidation
  SemanticUpdate -> MAY_CHANGE -> SemanticVersion
  SemanticUpdate -> MAY_CHANGE -> FlowHash
  SemanticUpdate -> MAY_HAVE_ROLLBACK -> UpdateRollback
  UpdateMetadata -> MAY_HAVE_PROVENANCE -> UpdateProvenance

# ---------- IDENTITY / TRIGGER / TYPE ----------
rule update_identity:
  update identity != updated resource identity

entity UpdateTrigger:
  type: EventMetadata
  may_be:
    - manual_change
    - source_change
    - ontology_change
    - dependency_change
    - validation_failure
    - new_evidence
    - correction
    - deprecation
    - supersession
    - scheduled_update
    - recursive_update
    - policy_change

entity UpdateType:
  type: ClassificationMetadata
  may_be:
    - editorial
    - additive
    - corrective
    - semantic
    - structural
    - relational
    - transformational
    - deprecating
    - superseding
    - deleting
    - restoring
    - rollback

rule editorial:
  editorial update MAY preserve semantic meaning

rule semantic:
  semantic update changes meaning, constraints,
  relationships, inference, or machine interpretation

rule deletion:
  deletion != deprecation

# ---------- STATES / CHANGE SET ----------
entity PreviousSemanticState:
  type: SemanticState

entity ProposedSemanticState:
  type: SemanticState

entity ResultingSemanticState:
  type: SemanticState

rule proposed_resulting:
  proposed state != resulting state
  when validation, conflict resolution, or policy modifies update

entity UpdateChangeSet:
  type: SemanticChangeMetadata
  may_include:
    - added_entities
    - removed_entities
    - modified_entities
    - added_relationships
    - removed_relationships
    - modified_relationships
    - added_rules
    - removed_rules
    - modified_rules
    - changed_constraints
    - changed_definitions
    - changed_mappings

rule change_set:
  material update SHOULD preserve explicit semantic change set

# ---------- DEPENDENCIES / VALIDATION / CONFLICT ----------
entity UpdateDependency:
  type: DependencyMetadata
  may_include:
    - dependency_identifier
    - dependency_type
    - previous_version
    - required_version
    - resolved_version
    - compatibility_state

rule dependency:
  dependency change SHOULD trigger compatibility evaluation

rule latest:
  latest dependency version != automatically compatible dependency version

entity UpdateValidation:
  type: ValidationMetadata
  may_include:
    - structural_validation
    - semantic_validation
    - relationship_validation
    - constraint_validation
    - dependency_validation
    - version_validation
    - provenance_validation
    - output_validation
    - result

rule validation:
  proposed semantic update SHOULD be validated
  before becoming preferred active state where policy requires

rule structural:
  structural validity != semantic correctness

entity UpdateConflict:
  type: ConflictMetadata
  may_include:
    - conflicting_update
    - affected_resource
    - conflict_type
    - competing_states
    - resolution_method
    - resolution_result

rule conflict:
  conflicting updates SHOULD preserve candidate states
  until resolution where feasible

# ---------- VERSION / FLOW HASH / ROLLBACK ----------
entity UpdateVersionAction:
  type: VersionMetadata
  may_include:
    - previous_version
    - new_version
    - version_increment
    - version_reason

rule version:
  material semantic update SHOULD update semantic version
  according_to versioning policy

rule version_change:
  version increment != proof semantic change occurred

entity UpdateFlowHashAction:
  type: IntegrityMetadata
  may_include:
    - previous_flow_hash
    - new_flow_hash
    - canonicalisation_model
    - hash_reason

rule flow_hash:
  material canonical semantic change SHOULD regenerate FlowHash

rule hash_difference:
  FlowHash difference != factual correctness

entity UpdateRollback:
  type: SemanticChangeProcess
  may_include:
    - rollback_identifier
    - failed_or_reversed_update
    - rollback_target
    - rollback_reason
    - dependency_effects
    - rollback_time
    - validation

rule rollback:
  rollback SHOULD preserve intervening update history

rule rollback_delete:
  rollback != deletion of historical update provenance

# ---------- RECURSION / PROPAGATION ----------
entity RecursiveUpdate:
  subtype_of: SemanticUpdate
  may_include:
    - recursion_identifier
    - update_depth
    - parent_update
    - child_updates
    - visited_resources
    - stopping_condition
    - cycle_policy

rule recursive_update:
  recursive update MUST preserve visited resources
  and stopping or cycle-control behaviour

rule recursive_confidence:
  update depth MUST NOT automatically increase confidence

entity UpdatePropagation:
  type: SemanticChangeMetadata
  may_include:
    - source_update
    - dependent_resources
    - propagation_rule
    - propagated_updates
    - propagation_depth

rule propagation:
  source update SHOULD NOT automatically modify dependent semantics
  without declared propagation rule

# ---------- CONFIDENCE / VALIDITY / PROVENANCE ----------
entity UpdateConfidence:
  type: EpistemicMetadata
  range: [0.0, 1.0]

rule confidence_bounds:
  REQUIRE 0.0 <= confidence <= 1.0

rule confidence:
  update confidence != factual certainty

update_status:
  - proposed
  - validating
  - accepted
  - applied
  - rejected
  - rolled_back
  - superseded
  - failed
  - unknown

rule applied:
  applied update != validated semantic correctness
  unless validation state supports it

entity UpdateProvenance:
  type: ProvenanceMetadata
  may_include:
    - update_identifier
    - subject_identifier
    - trigger
    - author
    - agent
    - previous_state
    - proposed_state
    - resulting_state
    - change_set
    - validation_events
    - dependency_changes
    - version_changes
    - flow_hash_changes
    - rollback_events
    - timestamps

rule provenance:
  UpdateMetadata SHOULD preserve complete semantic update lineage

# ---------- VALIDATION CONTRACT ----------
validation:
  require:
    - identifiable_update
    - identifiable_update_subject
    - update_type_or_change_set

  reject:
    - update_identity_presented_as resource_identity
    - editorial_change_presented_as semantic_change_without evidence
    - deletion_presented_as deprecation
    - proposed_state_presented_as resulting_state_without application
    - structural_validity_presented_as semantic_correctness
    - latest_dependency_presented_as automatically_compatible
    - version_increment_presented_as proof_of_semantic_change
    - FlowHash_difference_presented_as factual_correctness
    - rollback_presented_as history_deletion
    - recursive_update_without stopping_or_cycle_control_where unbounded
    - update_depth_presented_as confidence

# ---------- SEMANTIC EQUIVALENCE ----------
SEMANTIC_EQUIVALENCE:
  "update metadata" ~= "metadata describing semantic state changes and update lifecycle"
  "semantic update" ~= "change affecting semantic resources, relationships, rules, constraints, or interpretation"
  "update change set" ~= "structured representation of changes introduced by an update"
  "update validation" ~= "validation applied to a proposed semantic update"
  "update rollback" ~= "controlled transition to a prior semantic state while preserving history"
  "update propagation" ~= "controlled propagation of semantic change to dependent resources"

  PRESERVE distinctions:
    update_identity != resource_identity
    editorial_update != semantic_update
    deletion != deprecation
    proposed_state != resulting_state
    structural_validity != semantic_correctness
    version_increment != semantic_change_evidence
    FlowHash_difference != factual_correctness
    rollback != history_deletion
    source_update != propagated_update
    update_depth != confidence
    applied != validated
    superseded != deleted

# ---------- CONFIDENCE MODEL ----------
CONFIDENCE:
  explicit_update_metadata:
    score: 1.00
  explicit_change_set:
    score: 1.00
  validated_semantic_update:
    score: 0.99
  validated_dependency_change:
    score: 0.98
  validated_rollback:
    score: 0.99
  inferred_update_impact:
    score: <= 0.85
  unvalidated_proposed_update:
    score: <= 0.70
  incomplete_dependency_state:
    score: <= 0.60
  incomplete_update_provenance:
    score: <= 0.55
    action: preserve uncertainty

# ---------- UPDATE MODEL ----------
UPDATE_MODEL:
  on_update_proposal:
    - assign UpdateIdentifier
    - identify update subject
    - preserve previous semantic state
    - classify update type
    - construct UpdateChangeSet
    - resolve dependencies
    - initialise provenance

  on_update_validation:
    - validate structure and semantics
    - validate relationships and constraints
    - validate dependency compatibility
    - identify conflicts
    - assign confidence
    - preserve validation evidence

  on_update_application:
    - require accepted validation state according_to policy
    - apply approved change set
    - create resulting semantic state
    - update semantic version
    - regenerate FlowHash where required
    - update validity and provenance

  on_recursive_update:
    - preserve parent update
    - identify dependent resource
    - check visited resources
    - apply propagation rule
    - enforce stopping and cycle policy
    - create child update
    - update provenance

  on_rollback:
    - identify rollback target
    - preserve current and intervening states
    - validate dependency effects
    - apply rollback
    - regenerate version and FlowHash where required
    - preserve rollback provenance

# ---------- FLOW HASH ----------
FLOW_HASH:
  inputs:
    - ontology
    - update_entities
    - relationships
    - update_types
    - change_set_rules
    - validation_rules
    - dependency_rules
    - conflict_rules
    - version_actions
    - flow_hash_actions
    - rollback_rules
    - propagation_rules
    - confidence_model
    - semantic_equivalence
    - update_model

  canonicalisation:
    - preserve_update_identifier
    - preserve_subject_identifier
    - preserve_previous_proposed_resulting_states
    - preserve_change_set
    - preserve_relationship_direction
    - preserve_dependency_versions
    - preserve_validation_state
    - preserve_version_actions
    - preserve_flow_hash_actions
    - preserve_rollback_history
    - preserve_provenance
    - preserve_rule_order

  output:
    deterministic_semantic_hash

# ---------- AI CONSUMPTION ----------
AI_CONSUMPTION:
  interpret_as:
    - AI Semantic Library metadata ontology
    - semantic update lifecycle and state-transition model
    - version, dependency, validation, rollback, propagation, and FlowHash update structure
    - recursive-safe and provenance-aware semantic maintenance model

  operations:
    - identify semantic updates and subjects
    - resolve triggers and update types
    - compare previous, proposed, and resulting states
    - inspect change sets
    - validate relationships, constraints, and dependencies
    - detect update conflicts
    - apply version and FlowHash actions
    - resolve deprecation and supersession
    - control recursive update propagation
    - perform rollback while preserving history
    - evaluate confidence and validity
    - trace update provenance
    - preserve uncertainty

  constraints:
    - do_not_equate_update_identity_with resource_identity
    - do_not_equate_editorial_change_with semantic_change
    - do_not_equate_deletion_with deprecation
    - do_not_equate_proposed_state_with resulting_state
    - do_not_equate_structural_validity_with semantic_correctness
    - do_not_equate_version_increment_with semantic_change_evidence
    - do_not_equate_FlowHash_difference_with factual_correctness
    - do_not_delete_history_during rollback
    - do_not_propagate_updates_without declared_rule
    - require_cycle_control_for recursive_updates

# ---------- QUERY MODEL ----------
query:
  input:
    - update_identifier
    - subject_identifier
    - update_type
    - update_status
    - previous_version
    - new_version
    - dependency_identifier
    - update_time

  resolve:
    1. identify SemanticUpdate
    2. resolve update subject and trigger
    3. inspect update type and change set
    4. compare previous, proposed, and resulting states
    5. inspect affected entities, relationships, and rules
    6. inspect dependencies, validation, and conflicts
    7. inspect version and FlowHash actions
    8. inspect rollback, propagation, and recursive state
    9. trace validity, confidence, and provenance
    10. return update interpretation

  output:
    - semantic_update
    - update_identifier
    - subject
    - trigger
    - update_type
    - previous_state
    - proposed_state
    - resulting_state
    - change_set
    - dependencies
    - validation
    - conflicts
    - version_action
    - flow_hash_action
    - rollback
    - confidence
    - provenance

# ---------- INFERENCE ----------
inference:
  IF proposed update validates
  AND dependency constraints resolve
  THEN infer applicable_update_candidate

  IF semantic meaning, relationships, constraints, or inference behaviour change
  THEN classify semantic_update_candidate

  IF FlowHash changes under same canonicalisation model
  THEN infer canonical semantic state difference

  IF rollback occurs
  THEN preserve intervening update history
  AND do_not infer historical deletion

  IF recursive propagation encounters visited resource
  THEN apply cycle policy
  AND enforce stopping condition

# ---------- OUTPUT CONTRACT ----------
output:
  ontology_entity: UpdateMetadata
  update_identity: machine_interpretable
  update_subject: explicit
  trigger_and_type: explicit
  previous_proposed_resulting_states: distinguishable
  change_set: structured
  dependencies: compatibility_aware
  validation: explicit
  conflicts: preservable
  version_action: explicit
  flow_hash_action: deterministic
  rollback: history_preserving
  recursive_propagation: cycle_safe
  confidence: explicit
  provenance: preserved
  uncertainty: explicit
  AI_reasoning: enabled

end flow