On Friday local time, the first-stage booster of SpaceX’s upgraded “Starship” rocket malfunctioned during a pre-dawn test in Texas, which may complicate the company’s efforts to demonstrate the rocket’s lunar landing capability to NASA. SpaceX rolled the stainless-steel booster onto the test stand at the company’s Starbase rocket facility on Thursday, stating that it intended to test its redesigned propellant system and structural strength.

At approximately 4 a.m. Central Time on Friday, during testing on the test stand, an enlarged live video feed provided by SpaceX observation group LabPadre showed the booster suddenly invert and release a cloud of gas from the side, indicating that a pressure explosion may have blown open the booster’s exterior. SpaceX did not immediately respond to a request for comment on the incident.

The booster that suffered the accident on Friday is the first rocket of “Starship V3”. SpaceX stated that this iterative version of the rocket includes a series of new designs and features related to the lunar landing program. SpaceX is known for rapidly producing multiple iterative versions of boosters as part of its capital-intensive “test-and-fail” rocket development philosophy. However, it is unclear whether it has another V3 booster to resume testing, or how many months the incident will set back the Starship program.

Test the product over more than one session

A first conversation can show personality, but long-term quality appears only after the system has accumulated memory, preferences and notifications. Return later, change a preference and see whether the companion adapts without losing its core identity. Longitudinal testing also exposes repetition and stale context that a short demo cannot reveal.

Use controls as part of the quality test

Try the memory, notification, privacy and reset controls before you need them. A strong companion should make important settings understandable without forcing the user to delete the entire relationship to repair one problem. The best experience becomes more relevant over time while remaining easy to correct.

Look for continuity without constant callbacks

A companion should use remembered context when it helps, not repeatedly announce that it remembers. Good continuity reduces the need for the user to restate important information and makes recurring activities easier to resume. If every response references old history, personalization can feel forced rather than natural.

Check how the system handles a mistake

Correct a fact, reject a suggestion or change topic abruptly. The companion should repair the interaction and update the relevant state instead of arguing or repeating the same assumption later.

Evaluate whether the relationship remains user-led

Notifications, progression and premium features should support the user’s chosen interaction rather than manufacture urgency. Quiet hours, frequency controls and easy cancellation are practical signs that the product respects the user’s pace.

Compare richer media with the core conversation

Voice, images and video are valuable when they reinforce the same identity. If media quality is inconsistent or arrives too slowly, a simpler response may produce a better overall experience.

A final long-term check

Repeat the same test after several days and after changing one setting. AI products accumulate memory, synchronization state and billing or permission history, so problems may appear only after the first-session novelty has passed. The strongest products remain understandable as history grows: users can see what changed, correct the relevant state and continue without rebuilding the entire relationship.