Design capture. The gravity well Cameron wanted is real but it is not a radius - it is the controlled stretch of the network. A LIE body recalls any record still on the player's side, visibly reversing along its wire; capturing a switch (the hall access switch first) is how the well grows; commissioned machines create their devices, so the pilot bays yield the two-three early controlled devices. Disposals become a quality ladder - delete (leaves suspicious silence), delay, falsify (researched, trained on captured-traffic corpora), keep (into the player's archive as ordinary custody) - which closes the loop with research.md's training-data law. Dana's discover-and-reroute is captured as the facility counterplay seed. machine-work.md's pacing target is restated on the measured probe: the audit-cycle window is bought by a serviced chokepoint, not a LIE box's existence. Defense: docs-only design capture under the design-session workflow. detection.md owns the well, disposals, and counterplay; reach.md owns machines-as-devices; machine-work.md restates its own pacing clause; research.md gains only the linkage sentence; implementation is staged on ROADMAP #39 (stages 6-10), not begun here. The rejected radius and the reasons are recorded in the decision volume so it is not re-proposed.