The Synthetic Real: Episode 5 The Answer That Never Arrives
 In February 2022, an underwater robot called Boaty McBoatface was due back from a mission about 20 kilometers in under the Dotson Ice Shelf in Antarctica. It was supposed to return by midnight. According to a researcher aboard the expedition ship, the team lowered acoustic equipment into the water and tried to reach it for ten hours, 21 attempts at different spots. Nothing answered. The ship moved on to other work. At midnight the next night, the mission hit its time-out. The plan set before the dive was simple: if the mission was still running, abort it and come up to the surface for recovery. The team searched for three hours and found nothing. Late that night, satellite messages started coming in. Boaty had surfaced, and the ship went to get it. Nobody reached it during those two days. It surfaced the way it had been set up to before it went under. A Body Built for Silence Post four ended on a split. Whatever must be answered before the body falls stays in the body. Slower thinking can live somewhere else and arrive by radio. Underwater, the somewhere else barely exists. A research glider can't send or receive data while submerged; it has to surface to call in. On an earlier mission under a different ice shelf, the team had no communication with Boaty for 90 percent of its time in the water. So an ocean robot carries nearly everything, including what to do when things go wrong. One university's specification for a new research glider lists conditions, such as water leaking in, that must make it abort the mission and surface. For bodies like these, while they're under water or ice, losing the link isn't the emergency. It's the normal state. A Body Built for Contact A camera drone is the opposite. It's built to stay in touch with the controller in someone's hand. Many carry a setting for when that touch is lost. If the controller's signal drops for a few seconds, the drone does whatever its owner chose before takeoff: fly home, land, or hover. A rule like that can only use what was stored before the silence: where home is, and the assumption that the way back is clear. A drone flying home on its own can fly into something standing in the way. Somebody Wrote It Losing contact doesn't make a machine independent. It shows which rule was left in it. Any synthetic body that depends on a link carries one. Boaty's time-out, a glider's abort conditions, a drone's setting: every one existed before the silence did. With a drone, the somebody is literally the person holding the controller. Some bodies carry a second link for when the first one fails, and that is a choice made before launch too. In 2016, a research glider off the Great Barrier Reef stopped calling in three hours into its mission. Six days later it surfaced and called in on its backup transmitter, and the team recovered it. The damage, including a fragment of tooth lodged in its rear casing, showed a shark had attacked it. What a Fallback Can't Do A fallback protects the body. It doesn't finish the task. An aborted mission collects nothing more, and a drone that lands where it lost signal lands wherever that happens to be. A fallback also ends where the body's part ends. Boaty's time-out said when to come up, not where. By the time it surfaced, the ship was working somewhere else and had to cross over to reach it. The rule that runs when nothing answers is the one that was stored, and it can only work with what it was given. One More Thing A body's fallback rules are part of its design. Today, somebody writes them before the silence: an engineer setting a time-out, an owner choosing a setting before takeoff. The first post described a loop where a system specifies its own next body. If that loop closes, it writes these rules too. That's next. Discussed and drafted with the assistance of Claude (Opus 5.5) and Grok 4.7. Claims verified against primary sources.