IYABOKO Science & Technology Software-led · Hardware-enabled · Human-governed
Pricing
☰
Home
Products
AI Workspace Sentinel OS Education Pact Core OS
Solutions
Space OS Energy OS Environment OS Health & Biotech OS Quantum Net OS Financial Security OS
Pricing Login
Space OS · Space Systems Readiness

Prepare space systems for evidence-led readiness, review and responsible progression.

Space OS applies IYABOKO’s shared evidence, maturity, assurance and governance architecture to mission concepts, spacecraft and payload systems, communications, telemetry, simulation, orbital sustainability and qualification-readiness preparation.

Mission systems · Simulation · Telemetry · Evidence · Qualification-readiness planning · Human-governed review
Assess a Space Project Prepare in AI Workspace Discuss a Space Project Open Live Mission
Simulation-first Evidence-led Non-operational Human-governed
Space systemsMission, payload, communications and orbital context
H0–H6Visible maturity progression
Q0–Q5Evidence quality and confidence
Sentinel 20→36Readiness through deeper assurance
Operating Context

For early-stage and developing space work that needs structure before consequential decisions.

Space OS is designed for evidence preparation, simulation planning, architecture review and readiness progression. It helps organise what is known, what is assumed, what remains unverified and what requires qualified external review.

01

Mission & Payload Systems

Objectives, interfaces, mission logic, payload roles, subsystem assumptions and architecture dependencies.

02

Simulation & Digital Models

Scenario planning, model assumptions, SIL/MIL/HIL preparation, verification logic and evidence capture.

03

Telemetry & Communications

Telemetry pathways, command concepts, data exchange, ground–space communications and monitoring requirements.

04

Qualification Readiness

Requirements traceability, evidence gaps, environmental considerations, verification methods and specialist handoff preparation.

What Space OS Supports

Turn complex space-system work into traceable readiness decisions.

The goal is not to automate aerospace authority. The goal is to make the evidence, gaps, dependencies and next justified actions clearer before external technical, safety or regulatory decisions.

Architecture & Mission Planning

  • Mission concept framing
  • System and subsystem boundaries
  • Interface and dependency mapping
  • Assumption and requirement registers
  • Prototype / pilot pathway preparation

Simulation & Evidence

  • Scenario and simulation planning
  • Digital model evidence organisation
  • Test and verification planning
  • Telemetry evidence workflows
  • Evidence quality and maturity mapping

Readiness & Governance

  • Sentinel 20 readiness assessment
  • Sentinel 36 digital assurance
  • Findings and remediation cases
  • Independent closure preparation
  • External-review and authority handoff
Connected Products

Space OS is a domain solution built from the same four-product architecture.

It does not create a separate technology stack. The shared IYABOKO products are applied to the specific evidence, systems and review context of space work.

Prepare

AI Workspace

Research support, mission-context preparation, evidence organisation, technical writing and structured project material.

Open AI Workspace
Assess · Assure

Sentinel OS

Readiness assessment, digital assurance, findings, remediation cases, closure review and rescan-confirmed progression.

Explore Sentinel OS
Govern

Core OS

Evidence, H0–H6 maturity, Q0–Q5 quality, roles, authority, case state, auditability and bounded automation.

Explore Core OS
Build Capability

Education Pact

Learning and research capability pathways for space systems reasoning, evidence and responsible technology development.

Explore Education Pact
Space Readiness Workflow

Prepare → Assess → Assure → Remediate → Review → Progress.

Each stage should add evidence or resolve uncertainty. Progression is justified by the current state of the system, not by marketing claims.

01PrepareDefine mission context, requirements, assumptions and evidence.
02AssessUse Sentinel 20 to expose readiness gaps and boundaries.
03AssureUse Sentinel 36 to examine requirements, evidence, risks and dependencies.
04RemediateCreate governed cases with owners, actions and required evidence.
05ReviewSeparate remediation from closure and involve the appropriate reviewer.
06ProgressRescan, confirm the state and hand off to qualified authority where required.
Example Outputs

Produce artefacts that make the next decision easier to justify.

Outputs depend on scope and available evidence. They are readiness and preparation artefacts, not certificates of flight worthiness or regulatory approval.

MRB

Mission Readiness Brief

Mission context, assumptions, architecture status, maturity, dependencies and priority gaps.

SEP

Simulation Evidence Pack

Scenario logic, model assumptions, simulation outputs, limitations and verification status.

TRM

Telemetry Requirements Map

Telemetry needs, data pathways, command relationships, interfaces and evidence links.

ARM

Architecture Readiness Map

Subsystem relationships, interface dependencies, maturity position and unresolved assumptions.

QRM

Qualification Readiness Matrix

Requirements, verification methods, available evidence, missing evidence and specialist dependencies.

GOV

Governance & Handoff Pack

Findings, case status, closure evidence, residual issues and external-review requirements.

Evidence & Readiness

Make maturity and evidence quality visible before the next space-system decision.

Space OS inherits Core OS maturity and evidence architecture so early concepts are not presented as demonstrated capability.

H0–H6 MaturityTracks progression from early concept through increasingly controlled evidence and review stages.
Q0–Q5 Evidence QualityDistinguishes weak, incomplete or unverified evidence from stronger, traceable evidence.
Sentinel FindingsTurns material gaps into explicit requirements, owners, remediation actions and review states.
Rescan ConfirmationChecks whether remediation changed the original finding rather than assuming completion equals closure.
SpaceCore · IOSTS Public Engineering Experience

Explore the pathway from spacecraft simulation to evidence, assurance and accountable human review.

SpaceCore is the public engineering demonstration layer within Space OS. It connects the IOSTS-R research track, simulated spacecraft telemetry, digital-twin state, requirements, evidence, verification, Sentinel assurance and human-gate logic while keeping operational and flight-authority boundaries explicit.

Open Live Mission Discuss Research Collaboration View IOSTS Programme
Public engineering boundary: the SpaceCore interfaces are developmental simulation and evidence-readiness demonstrations. They are not connected to a physical spacecraft and do not provide flight authority, launch approval, certified avionics or operational mission control.
IOSTS-R PUBLIC MISSION SIMULATION

Engineering the pathway from evidence to space.

IYABOKO SpaceCore connects spacecraft simulation, requirements, telemetry, digital twins, evidence, verification, Sentinel assurance and accountable human decisions.

Open Live Mission
IYABOKO
Public Demo Session
T+ 00:00:00
Programme
IOSTS-R
Verification
PASS
Sentinel OP-30
HUMAN REVIEW
Flight Authority
NONE
IOSTS PROGRAMMES

Two research tracks. One evidence boundary.

IOSTS-R focuses on engineering with demonstrated technology. IOSTS-X provides a controlled research environment for speculative future-physics hypotheses without presenting them as demonstrated systems.

DEMO ACTIVE
REAL-WORLD ENGINEERING TRACK

IOSTS-R

Orbital research spacecraft development through baseline control, R1 integrated simulation, telemetry, digital twin, verification and evidence-centred human gates.

EXPERIMENTAL
FUTURE-PHYSICS RESEARCH TRACK

IOSTS-X

Intergalactic research concepts can be modelled, questioned and visualized, but remain under research HOLD until supported by falsifiable and reproducible evidence.

LIVE DEMONSTRATOR

Explore the spacecraft. Disturb the mission. Watch the evidence respond.

Change vehicle profile, camera view, spacecraft configuration and simulated subsystem conditions. SpaceCore changes assurance state rather than hiding the consequences.

IYABOKO Spacecraft Live Demonstrator

IOSTS-R research spacecraft simulation with evidence-centred SpaceCore assurance.

LIVE SIMULATION IOSTS-R SIMULATED TELEMETRY FLIGHT AUTHORITY NONE
NOMINAL
LOW EARTH ORBIT SIMULATION
T+ 0000 s
IYABOKO IOSTS-R / IYABOKO SPACECORE CONCEPTUAL SIMULATION ARTICLE
Physics basis: demonstrated / conventional simulation Physical spacecraft: NOT CONNECTED
Orbit / Phase
LEO
~550 km simulated
Velocity
7.61 km/s
simulated state
Battery
84.0 %
model estimate
Bus Power
38.0 W
simulated load
Temperature
29.0 °C
nominal
Communications
LINKED
98 % simulated quality

SpaceCore Assurance

Evidence CURRENT / SIMULATED Q3
Verification PASS
Sentinel OP-31 PASS
Sentinel OP-30 HUMAN REVIEW REQUIRED
READY FOR HUMAN GATE — no automatic advance.
Engineering boundary

SpaceCore shows what has been demonstrated, what changed, what evidence exists, and which human decision remains.

Live Demonstration Controls

These controls modify browser-side simulation state only. They do not communicate with spacecraft hardware, propulsion systems, HIL equipment or flight systems.

Engineering Event Stream

Digital Twin State

Model Truth AVAILABLE
Sensor State SIMULATED / VALID
Software State SIMULATED
Physical State NOT CONNECTED
IOSTS-X mode

The intergalactic profile is intentionally treated as experimental research. Speculative physics cannot be promoted to demonstrated engineering evidence without falsifiable, reproducible evidence.
Public Demonstration Notice

This interface is a simulated IYABOKO / IOSTS spacecraft demonstrator. The spacecraft image is a conceptual visualization. The telemetry is generated in the visitor’s browser and is not received from a physical spacecraft. IOSTS-X represents speculative future-physics research and is not presented as demonstrated intergalactic propulsion.

Flight Authority: NONE
EVIDENCE-CENTRED ASSURANCE

SpaceCore does not declare a spacecraft safe.

It shows what has been demonstrated, what has not, what configuration generated the evidence, what changed, what remains uncertain and which accountable human decision must happen next.

Current State → Target → Requirement → Evidence → Gap → Action
Hard-gate boundary

OP-30 failure, Bede boundary violation, invalid authority, critical DouPeka anomaly, insufficient evidence or configuration/evidence incoherence prevents unsupported progression.
Evidence CURRENT / SIMULATED Q3
Verification PASS
Sentinel OP-31 PASS
Sentinel OP-30 HUMAN REVIEW REQUIRED
SPACECORE

Evidence-centred space systems engineering infrastructure.

01

Mission & Twin

Mission simulation, telemetry, model truth, observed state, residuals and anomaly response.

02

Verify

Requirements, configurations, test evidence, applicability, Q-level and verification state.

03

Graph

Trace mission, requirement, configuration, model, test, evidence, verification and findings.

04

Sentinel

Core 20 reasoning principles and 36 operational assurance rules with hard gates.

05

Lab

Simulation, testing, findings, root cause, remediation, retest and regression.

06

Assure

H/Q/O maturity, independent evidence, Sentinel conditions, human authority and gates.

07

Reports

Immutable engineering snapshots, review history, release packages and provenance.

08

AI Advisor

Analyse, explain and identify gaps. AI authority remains NONE for engineering gate decisions.

IOSTS-R DEVELOPMENT PATH

Progress is evidence-gated, not presentation-gated.

The roadmap below is the programme model demonstrated by SpaceCore. Future stages require their own engineering evidence and human decisions.

R0
Baseline
Mission definition, requirements, system boundaries and configuration baseline.
R1
Integrated Simulation
Coupled Power, Thermal, Avionics, Communications, Telemetry and FDIR demonstration.
R2
Bench Evidence
Controlled low-energy engineering breadboard evidence when physical work is authorised.
R3
SIL / MIL / HIL
Model truth, sensor state, software state and physical state remain independently identified.
R4
Engineering Model
Developmental engineering model only after prior evidence supports the transition.
R5
External Review
Independent engineering review of configuration, evidence, verification, findings and assumptions.
R6
Flight Candidate
Conditional future designation only if required evidence, boundaries and external authorities are satisfied.
ENGINEERING REVIEW

Don't ask whether the spacecraft is ready. Ask to see the evidence.

Explore the live demonstrator, inspect SpaceCore assurance logic, and follow the evidence chain from requirement through verification and human review.

Open Live Demonstrator View Assurance Model
Demonstration boundary

Public IYABOKO interfaces use conceptual spacecraft visuals and simulated engineering data. They do not command hardware, certify spacecraft safety, authorize launch or create regulatory or flight authority.

IOSTS-X is explicitly speculative research and requires falsifiable evidence before any hypothesis could move toward demonstrated engineering status.

Flight Authority: NONE

Start with the space-system evidence you already have.

Prepare the project in AI Workspace, assess readiness through Sentinel 20, or discuss a defined space project when deeper review and assurance are justified.

Assess a Space Project Prepare Evidence Discuss a Project