FREQUENTLY ASKED QUESTIONS
OSOIX FAQ
Clear answers about what OSOIX is, what is live today, how evidence is labelled, what customer access means, and where the platform deliberately stops.
OSOIX is an active-development intelligence and verification platform. It does not provide autonomous spacecraft command, custody of customer assets or private-key intake. Mission intelligence recommends; humans authorize.
What is OSOIX?
OSOIX is the intelligence and verification layer being built for orbital infrastructure. It combines modeled orbital state, public and authorized observations, evidence, mission context, customer workspaces and human review into read-only decision-support surfaces.
Is OSOIX live today?
The web platform, public Intelligence Grid, Orbital Twin, evidence systems, Mission Control software and customer portal are deployed software services. This does not mean OSOIX has flight heritage, direct spacecraft telemetry by default, autonomous flight authority or commercial flight deployment.
Can OSOIX control a spacecraft automatically?
No. The current architecture keeps commandPath=false and automaticActionAllowed=false. Mission Control and customer access do not create an uplink or command path. Human authorization remains required for any real-world operational action.
What do live, near-live and modeled state mean?
Live means a source is being received or a provider claims a continuous live transport. Near-live camera products are verified image frames refreshed on a bounded schedule. Modeled orbital state is computed from current orbital elements and must never be presented as direct onboard telemetry.
Are the public cameras continuous live video?
Not generally. Most public ground-camera sources used by OSOIX are near-live image frames or snapshots. They are refreshed, freshness-scored and failed over when necessary. Official video embeds such as NASA ISS streams are treated separately, and provider availability is not presented as proof that every rendered frame is live.
What does the customer portal provide?
The commercial architecture supports orbital monitoring, spacecraft telemetry workspaces, historical replay, advanced analytics, alerts, reports and exports, API access and team workspaces. Access is entitlement-based and never grants Mission Control authority.
Is OSOIX charging customers or publishing final pricing now?
The commercial billing architecture is implemented with fail-closed launch controls, Stripe event verification and server-side entitlements, but the live commercial launch remains separately gated. Final public pricing should only be treated as valid when it is explicitly published and the launch gate is approved.
How is OSOIX secured?
OSOIX uses server-side authorization, signed sessions, no-store operational responses, fail-closed service boundaries, evidence integrity controls and post-quantum readiness work including ML-DSA-65 and ML-KEM-768 runtime verification alongside conventional cryptography. Security claims are bounded to what is actually implemented and verified.
How does the OSOIX PWA work offline?
Operational PWAs are intentionally live-only. Authenticated or operational pages are not cached by the service worker, failed mutations are not replayed, and offline operational navigation returns an explicit unavailable state rather than stale mission or customer data.
Does OSOIX hold private keys, custody assets or replace human operators?
No. The current commercial and operational contracts explicitly keep custodyAuthority=false, privateKeyIntake=false and humanAuthorizationRequired=true. OSOIX is designed to assemble evidence, expose uncertainty and support bounded decisions—not silently take ownership or operational authority.