One journey. One connected architecture.

Program state

Concept and system development.

The current phase is focused on defining the program: the human and mission requirements it must address, the systems those requirements influence and the evidence needed to advance. This brief describes architectural intent rather than completed hardware.

Core objective

Connect person, vehicle and operations.

A personal objective becomes a mission profile. The mission profile informs the cabin. The cabin shapes the spacecraft. Vehicle and cabin state connect to the digital system and mission team. The architecture is designed to preserve that line of reasoning from end to end.

System structure

Design the interfaces, not only the components.

Many of the program’s most important questions sit between systems: how the person receives information, how the cabin influences vehicle constraints, how autonomy supports operators and how return requirements affect the complete mission.

Development pathway

Move from definition to evidence.

The proposed progression begins with requirements and architecture, then moves through simulation, physical subsystem prototypes, integrated ground demonstration and future flight validation. Each stage is intended to reduce a defined area of uncertainty.

Public record

Make maturity visible.

Future releases will distinguish design studies from simulation, prototypes from tests and technical evidence from concept visualization. Each update will identify its method, learning and relationship to the next development decision.