ROADMAP #39 stage 6, the first slice of the territory well. install_machine_device gives every owned machine a player-controlled interface auto-wired to the switch serving its area, and reconcile_work_grid keeps that true as the fleet grows. That closes the gap the pacing probe found: a networked machine whose logs had a carrier but whose owner had no custody surface. Sim::recalls reports each record pulled back this tick and all three frontends walk it backward along its own wire, so direction carries the read - crimson coming home is a catch. Measured to the audit at tick 8000: THINK with no cover loses (0 of 38 stopped, Dana Convinced); THINK with a LIE machine one bay away still loses, because both machines are leaves off facility switching and their controlled stretches never join; THINK with the hall switch captured stops 38 of 38 and Dana stays Cold. The middle row is the ladder, not a bug. The act-one quiet-exit test proved it independently: adding devices made a previously silent THINK rack start authoring, the scripted exit broke, and it passes again once the script captures the chokepoint first. Defense: implements reach.md's commissioned-machine-is-a-device clause and the recall half of detection.md's territory well, both adopted earlier today; their status notes now say what landed. The remaining well stages - silence-as-anomaly and Dana's reroute - are named as open, and the log records that concealment is currently perfect until they exist, so the pacing target cannot yet be judged. No save-format change: the recall readout is per-tick and devices are existing persisted state.