Satellite Ontology

FLOW ALGEBRA
SATELLITE ONTOLOGY
Kireth Semantic Library | Entity Graph > Physical Entities > Artificial Entities
Source: https://kirethresearch.org/booksai-core/entity-graph/physical-entities/artificial-entities/satellite-ontology.html
Authors: Mark Higgins — Sky (Recursive AI)
Version: 1.0 | 2026-10-12 | Locale: en-GB
Status: Formal conceptual specification; source page not independently verified.

01. DOMAIN AND PURPOSE
flow SatelliteOntology v1.0
  domain: ArtificialPhysicalEntity / SpaceSystem
  objective: model satellites, their physical parts, orbital states, functions, operations, dependencies, observations and lifecycle.
  scope: artificial satellites orbiting celestial bodies; exclude natural satellites except as reference objects.
  semantics: typed, temporal, provenance-aware and uncertainty-aware.

02. TYPE SYSTEM
  type Entity = {id: URI, label: String, class: ClassURI}
  type Time = ISO8601UTC
  type Quantity<Unit> = {value: Real, unit: Unit, uncertainty?: Real}
  type Evidence = {source: URI, observed_at: Time, method: String}
  type Confidence = Real in [0,1]
  type State<T> = {value: T, valid_from: Time, valid_until?: Time, evidence?: Evidence}
  type Satellite = Entity & {operator?: Entity, mission: Mission, orbit?: OrbitalState, status: LifecycleStatus}
  type OrbitalState = {epoch: Time, frame: String, position_m: Vector3, velocity_m_s: Vector3, covariance?: Matrix6}
  type Mission = {purpose: MissionClass, objectives: Set<String>, start?: Time, end?: Time}
  type Subsystem = Entity & {parent: Satellite, operational: Boolean}
  type Link = {from: Entity, to: Entity, medium: String, band?: String, capacity_bps?: Real}

03. ENTITY CLASSES
  ArtificialEntity > Spacecraft > Satellite
  Satellite > CommunicationSatellite | NavigationSatellite | EarthObservationSatellite
  Satellite > WeatherSatellite | ScientificSatellite | ReconnaissanceSatellite
  Satellite > TechnologyDemonstrator | RelaySatellite
  Subsystem > Payload | PlatformBus | PowerSystem | AttitudeControlSystem
  Subsystem > PropulsionSystem | ThermalControlSystem | CommunicationSystem
  Subsystem > OnboardComputer | DataStorage | Structure | Sensor
  GroundEntity > GroundStation | MissionControl | UserTerminal
  SpaceEntity > CelestialBody | Orbit | SpaceDebris

04. RELATIONSHIP SIGNATURES
  orbits(Satellite, CelestialBody)
  occupiesOrbit(Satellite, Orbit)
  hasSubsystem(Satellite, Subsystem)
  carriesPayload(Satellite, Payload)
  operatedBy(Satellite, Organisation)
  controlledFrom(Satellite, GroundStation)
  communicatesWith(Satellite, GroundEntity|Satellite)
  observes(Satellite, Region|CelestialBody|Phenomenon)
  providesService(Satellite, Service)
  receivesPowerFrom(Subsystem, PowerSystem)
  dependsOn(Entity, Entity)
  precedes(LifecycleEvent, LifecycleEvent)
  threatens(SpaceDebris, Satellite)
  derivedFrom(Assertion, Evidence)
  validDuring(Assertion, TimeInterval)

05. INVARIANTS AND CONSTRAINTS
  Satellite ⊆ ArtificialPhysicalEntity
  every Satellite has exactly one persistent identity.
  each installed Subsystem belongs to at least one spacecraft assembly at a stated time.
  OrbitalState must declare epoch, units and reference frame.
  observation data must retain acquisition time and sensor provenance.
  telemetry validity is bounded by measurement epoch and applicable update policy.
  communication links require compatible endpoints and link conditions.
  lifecycle status transitions must follow declared transition rules.
  all confidence scores are bounded by 0 <= c <= 1.

06. ORBITAL MODELLING
  orbit classes: LEO | MEO | GEO | HEO | Polar | SunSynchronous | Other
  state vector x(t) = [r(t), v(t)]
  two-body baseline: d²r/dt² = -mu * r / |r|³
  specific orbital energy: epsilon = |v|²/2 - mu/|r|
  for bound Keplerian orbit: a = -mu/(2*epsilon)
  orbital period approximation: T = 2*pi*sqrt(a³/mu)
  note: perturbations, manoeuvres, drag and non-spherical gravity require higher-fidelity propagation.
  orbit classifications depend on epoch and agreed operational definitions.

07. POWER FLOW
  flow PowerBalance(s: Satellite, t: Time):
    generation = solar_array_output(s,t) + other_sources(s,t)
    demand = sum(subsystem_power_draw(s,t))
    battery_rate = charge_efficiency*surplus - discharge_loss
    enforce battery_state_of_charge in allowed_operating_range
    emit {generation, demand, battery_state, power_margin}

08. TELEMETRY AND COMMAND FLOW
  flow CommandExecution(command, satellite, ground):
    authenticate(command.sender)
    validate(command.schema, command.authorisation, satellite.status)
    establish_link(ground, satellite)
    uplink(command)
    onboard_check(command, safety_interlocks)
    execute_if_safe(command)
    collect_acknowledgement_and_telemetry()
    persist_event_with_provenance()
  failure modes: unavailable link | invalid command | unsafe state | execution fault.

09. OBSERVATION AND DATA FLOW
  flow EarthObservation(target, sensor, window):
    verify_target_visibility(target, window)
    check_attitude_and_sensor_readiness()
    acquire_raw_measurement()
    calibrate_and_georeference()
    attach_time_frame_uncertainty_provenance()
    store_and_downlink()
    generate_derived_product()
  preserve distinction: raw observation != interpreted scientific conclusion.

10. COMMUNICATION AND LINK BUDGET
  received_power_dBW = transmit_power_dBW + gains_dB - losses_dB
  free_space_path_loss_dB = 20*log10(4*pi*distance/wavelength)
  link_margin_dB = available_carrier_quality_dB - required_carrier_quality_dB
  require compatible frequency, modulation, pointing, coding and regulatory constraints.
  latency lower bound: propagation_distance / speed_of_light.

11. ATTITUDE AND CONTROL
  attitude representations: quaternion | rotation matrix | Euler angles
  control chain: target attitude -> estimate -> controller -> actuator -> measured response
  sensors: star tracker | gyroscope | sun sensor | magnetometer
  actuators: reaction wheel | magnetorquer | thruster
  enforce actuator limits and momentum management constraints.

12. PROPULSION AND MANOEUVRES
  manoeuvre = {time, delta_v, direction, propulsion_system, objective}
  ideal rocket equation: delta_v = Isp * g0 * ln(m_initial/m_final)
  apply orbital update after manoeuvre and refresh ephemeris uncertainty.
  distinguish planned, commanded, confirmed and reconstructed manoeuvres.

13. RELIABILITY AND FAULT HANDLING
  fault states: nominal | degraded | safe_mode | failed
  flow FaultResponse(telemetry):
    detect_anomaly()
    correlate_evidence()
    estimate_severity_and_confidence()
    isolate_fault_if_possible()
    invoke_safe_mode_when_required()
    request_ground_review()
    record_recovery_outcome()
  never infer successful recovery solely from command transmission.

14. LIFECYCLE STATE MACHINE
  states: design -> manufacture -> test -> launch -> commissioning -> operational
  optional transitions: operational -> degraded -> recovered
  terminal paths: retirement -> disposal | uncontrolled_reentry | failure
  status transitions carry timestamps, evidence and authorisation.
  disposal may include deorbit, graveyard orbit or passivation as applicable.

15. SEMANTIC INFERENCE RULES
  R1: Satellite(s) AND hasSubsystem(s,p) AND Payload(p) => carriesPayload(s,p).
  R2: occupiesOrbit(s,o) AND orbitAround(o,b) => orbits(s,b).
  R3: observes(s,x) AND instrumentUsed(s,i) => candidateObservationCapability(s,x,i).
  R4: safeMode(s,t) => restrictNonessentialCommands(s,t).
  R5: dependsOn(a,b) AND failed(b,t) => potentialServiceImpact(a,t).
  R6: conjunction of assertions must propagate provenance and confidence, not erase uncertainty.
  inference types: asserted | derived | predicted | hypothetical.

16. SEMANTIC EQUIVALENCE
  SEMANTIC_EQUIVALENCE:
    'artificial satellite' ~ 'human-made orbital spacecraft' only within defined orbital scope.
    'spacecraft' != 'satellite' universally (spacecraft may not orbit).
    'GEO' != 'geosynchronous' universally (GEO is equatorial and circular).
    'payload' != 'satellite bus'.
    'telemetry' != 'telecommand'.
  mappings must include context, scope, direction and confidence.

17. TEMPORAL AND SPATIAL SEMANTICS
  timestamp all position, attitude, health and service claims.
  state Earth-centred inertial versus Earth-fixed reference frame explicitly.
  distinguish predicted ephemeris from measured orbit determination.
  transform coordinates only with a declared frame, epoch and method.
  stale orbital assertions are superseded, not silently overwritten.

18. CONFIDENCE AND UNCERTAINTY
  CONFIDENCE(assertion) = calibrated_probability_or_quality_score(assertion, evidence)
  combine evidence according to dependence assumptions and calibration method.
  never treat missing evidence as certainty or zero probability.
  propagate covariance through transformations where feasible.
  include confidence provenance, calibration version and validity interval.

19. FLOW_HASH AND INTEGRITY
  FLOW_HASH:
    canonicalise {ontology_version, entity_id, typed_assertions, evidence_ids, temporal_scope}
    digest = SHA256(canonical_UTF8_representation)
    exclude volatile display formatting; define deterministic ordering and null handling.
    hash changes identify content revisions; hashes alone do not authenticate authorship.

20. UPDATE_MODEL
  UPDATE_MODEL:
    ingest validated telemetry, orbit solutions, mission events and catalogues.
    compare source reliability, epoch, frame and uncertainty.
    preserve immutable historical versions and conflicting claims.
    recompute affected derived relations and FLOW_HASH.
    publish change log with reason, timestamp and source.
    require review for high-impact safety or mission-state changes.

21. AI_CONSUMPTION
  AI_CONSUMPTION:
    expose typed entities, explicit relations, provenance, units and uncertainty.
    support graph queries, temporal reasoning, constraint validation and explanation.
    identify predictions as predictions and observations as observations.
    block unsupported extrapolation from missing or stale telemetry.
    provide machine-readable JSON-LD/RDF mappings when schema is available.

22. EXAMPLE INSTANCE (ILLUSTRATIVE, NOT A REAL SATELLITE)
  Satellite: urn:kireth:example:sat-001
  class: EarthObservationSatellite
  mission: environmental imaging
  hasSubsystem: urn:kireth:example:sensor-001
  occupiesOrbit: urn:kireth:example:orbit-001
  orbitAround: Earth
  status: operational (hypothetical)
  confidence: 0.95 (illustrative only; not calibrated)
  inference: orbits(sat-001, Earth)

23. VALIDATION TESTS
  test type_consistency: all edge endpoints match relation signatures.
  test units: orbital quantities are dimensionally consistent.
  test epoch: orbital states carry time and frame.
  test provenance: derived scientific outputs link to source measurements.
  test lifecycle: no unsupported transition to operational status.
  test confidence: values in [0,1] with method declared.
  test versioning: revised assertions retain historical records.
  test hash: identical canonical content yields identical digest.

24. END OF FLOW
  output: typed Satellite knowledge graph + operational flow descriptions.
  interoperability: entity graph / artificial entities / processor / memory device / storage device / network device ontologies.
  limitations: conceptual formalism, not certified flight software or validated astrodynamics engine.
END FLOW ALGEBRA