1. When the machine is pushed to the edge on purpose

Tom Wolfe’s The Right Stuff returns as the recalled work because test pilots deliberately fly aircraft past their comfort zones to find out where they break. The desktop does not have pilots, but it does have degraded modes. The platform segment split and degraded-mode test is the program’s way of pushing the platform to the edge in a controlled way.

This entry explains why the platform segment split and degraded-mode test matters.

2. Why subsystem and integrated tests are not enough

The desktop has been tested as parts and as a whole platform:

  • Power distribution, thermal balance, network reconfiguration, autonomous swap.
  • Integrated system behavior and end-to-end mission simulation.

These tests prove that the platform works under expected conditions. They do not prove that a separated segment can survive when it suddenly has fewer resources and no one watching.

A segment split is a specific kind of failure: one part of the platform becomes independent. The degraded-mode test verifies that the segment can keep critical functions alive with reduced power, compute, thermal margin, and communications.

3. The failures that only appear after a split

Real splits expose problems that do not appear in normal operation:

  • A segment discovers that its battery is smaller than the platform-level thermal model assumed.
  • A service that was running on the separated segment tries to talk to the main platform and hangs instead of failing over.
  • The segment’s radio cannot maintain a ground link from its new attitude because its antenna pattern was designed for the combined stack.
  • A workload that was live-migrated before the split cannot resume because the target cell has a different firmware version.
  • The segment runs out of power because it does not know which non-critical loads to shed.

These are not single-subsystem problems. They emerge from the transition from one platform to two.

4. What this test must cover

The platform segment split and degraded-mode test must exercise:

  • A commanded split under nominal load.
  • A fault-triggered split, such as a simulated debris hit or cell failure.
  • Segment survival with reduced power, thermal, compute, and communications resources.
  • Service shedding and re-prioritization after the split.
  • Ground-link loss and recovery for the separated segment.
  • Rejoin readiness, even if no physical rejoining is attempted yet.

The goal is to prove that split-ready design is actually survivable.

5. What this changes

  • Platform segment split and degraded-mode testing is identified as the next qualification step for the desktop.
  • The test must verify segment-level survival, not just platform-level functionality.
  • The next entry will define the test matrix.