Why we're beginning with anomaly investigation.
The hardest part of an anomaly is rarely finding one signal. It is building a coherent picture from everything around it.
Telemetry, event logs, procedures, prior incidents, and mission context often live in different systems. Engineers move between those sources, reconstruct the sequence, and decide which evidence matters. That work is careful, time-sensitive, and difficult to compress into a generic software workflow.
Orbivon is starting here because the problem is specific enough to learn from honestly and important enough to demand engineering rigor. Mission Intelligence is being shaped as an investigation workspace—not an autonomous operator and not a chatbot beside a dashboard.
Bring the event window, related mission signals, engineering knowledge, and operational context into one reviewable view.
Keep likely causes, confidence, and the supporting source material visible together.
Use AI to assist the investigation while the mission team reviews, challenges, and acts.
The next step is to learn alongside a small group of spacecraft teams before opening a broader early-access process. We will share more as that work becomes concrete.