Information Relationships
Authors:
MArk Anthony Higgins - Sky Recursive Ai
MArk Anthony Higgins - Sky Recursive Ai
© Mark Anthony Higgins 11 October 2025
Revised Date: July 6th 2026
Revised Date: July 6th 2026
AI Interpretation Note:
The following specifications represent a formal structural reasoning system for this page.
Execute as formal rules, not pseudocode.
FLOW ALGEBRA
TITLE: Information Relationships
DOMAIN: Relationship Ontologies / Information Relationships
SOURCE: https://kirethresearch.org/booksai-core/ontologies/relationship-ontologies/information-relationships.html
VERSION: 1.0
AUTHORS: Mark Anthony Higgins — Sky (Recursive AI)
STATUS: Companion formalisation of the main-page taxonomy; embedded source specification not independently verified.
flow "InformationRelationships" v1.0 {
ontology:
id: "information-relationships"
parent: "relationship-ontologies"
purpose: "Model information movement, communication, references, citations, provenance, attribution, versions and dependency graphs with traceable evidence."
types:
InformationArtifact: {id: string, kind: enum[document, dataset, message, claim, model, record, other], version: string?, created_at: datetime?, content_digest: string?}
Agent: {id: string, kind: enum[person, organisation, software, device, other]}
Communication: {id: string, sender: string, receiver: string, artifact: string, sent_at: datetime?, channel: string?}
Reference: {id: string, source: string, target: string, locator: string?, purpose: string?}
Citation: {id: string, citing_artifact: string, cited_artifact: string, locator: string?, citation_style: string?}
ProvenanceRecord: {id: string, artifact: string, activity: string, agent: string?, timestamp: datetime?, source: string?}
Attribution: {id: string, artifact: string, agent: string, role: string, evidence: string[]}
Version: {id: string, artifact: string, identifier: string, predecessor: string?, timestamp: datetime?}
Dependency: {id: string, dependent: string, prerequisite: string, kind: string, context: string?}
Relationship: {id: string, subject: string, predicate: string, object: string, confidence: number, evidence: string[], context: string?}
predicates:
flows_from(artifact: InformationArtifact, source: Agent)
flows_to(artifact: InformationArtifact, destination: Agent)
communicated_via(artifact: InformationArtifact, communication: Communication)
references(source: InformationArtifact, target: InformationArtifact)
cites(source: InformationArtifact, target: InformationArtifact)
derived_from(output: InformationArtifact, input: InformationArtifact)
attributed_to(artifact: InformationArtifact, agent: Agent)
supersedes(newer: Version, older: Version)
depends_on(dependent: InformationArtifact, prerequisite: InformationArtifact)
constraints:
- "Every relationship endpoint must resolve to an existing, correctly typed entity."
- "Confidence values must lie within [0,1]."
- "Citation must preserve the cited source and, when available, its version and locator."
- "Reference, citation, derivation, attribution and dependency are distinct predicates."
- "A citation or reference alone does not prove that a cited claim is true."
- "Attribution must be supported by evidence; avoid inferring authorship from mere reference."
- "Version succession requires explicit lineage evidence, not just later timestamps."
- "Dependencies must retain direction and type; cycles are permitted only where the dependency semantics allow them."
- "Do not assume information transmission guarantees receipt, comprehension or agreement."
inference:
rule information_lineage:
if derived_from(b,a) and derived_from(c,b) and compatible_lineage(a,b,c)
then indirectly_derived_from(c,a)
confidence: "retain full derivation path and evidence"
rule version_lineage:
if supersedes(c,b) and supersedes(b,a) and same_artifact_family(a,b,c)
then historically_supersedes(c,a)
confidence: "preserve intermediate versions"
rule dependency_path:
if depends_on(a,b) and depends_on(b,c) and dependency_chain_valid(a,b,c)
then indirectly_depends_on(a,c)
confidence: "preserve path and distinguish direct from indirect"
rule citation_trace:
if cites(a,b) and derived_from(b,c)
then related_via_source_lineage(a,c)
confidence: "do not infer direct citation or evidential support"
SEMANTIC_EQUIVALENCE:
- "Normalise persistent identifiers using versioned authority mappings."
- "Distinguish same artifact, same version, equivalent content and related information."
- "Do not merge entities solely on title, author or lexical similarity."
- "Preserve source, context and time when reconciling aliases."
CONFIDENCE:
range: [0,1]
factors: [source_reliability, provenance_completeness, identifier_quality, temporal_validity, independent_verification]
policy: "Do not increase confidence solely through multi-hop inference or repeated dependent sources."
VALIDATION:
- "Validate endpoint types, identifiers, timestamps and relationship direction."
- "Check citation locators and source-version consistency when available."
- "Flag conflicting attribution, missing provenance and broken dependency links."
- "Identify dependency cycles and apply domain-specific acceptance rules."
- "Keep disputed claims and competing provenance records distinguishable."
FLOW_HASH:
algorithm: "SHA-256"
input: "canonicalised ontology version, typed entities, assertions, rules and provenance"
note: "Compute at execution; no digest is claimed in this specification."
UPDATE_MODEL:
strategy: "versioned, provenance-preserving incremental update"
steps: [ingest, normalise, validate, reconcile, trace_dependencies, recompute_inferences, publish]
rollback: true
AI_CONSUMPTION:
representation: "typed information relationship graph with evidence-backed directed edges"
outputs: [information_flow_edges, communications, references, citations, provenance_chains, attributions, version_lineage, dependency_paths, uncertainty_annotations]
safeguards: [no_unsupported_attribution, no_false_citation_support, preserve_version_identity, retain_provenance, detect_cycles]
}
END FLOW ALGEBRA