Physical layer enables software control

The real edge is not the low margin work itself, it is that owning the messy physical layer lets Atoms become the system that decides how the whole operation runs. In food, CloudKitchens and Lab37 put Atoms inside the kitchen layout, order flow, and robot workflow, which makes Otter harder to replace. In mining, Pronto wins by retrofitting existing trucks, then sits above dispatch, route learning, safety, updates, and monitoring, where software margins are better.

• CloudKitchens gives Atoms control of the building and daily workflow. A restaurant rents the kitchen, then order routing, courier handoff, and robotic assembly can be designed around that space from day one. That makes the software layer part of the operating environment, not just another app on top.
  1 sacra 2 cloudkitchens
• Otter is the high margin control point because it becomes the screen where orders, payments, kiosks, online checkout, and kitchen status meet. Once a restaurant runs every channel through one queue and payment stack, swapping out the software risks breaking store operations and losing order volume.
  1 sacra 3 tryotter 4 tryotter 6 tryotter
• Pronto uses the same pattern in mining. Mines keep Caterpillar, Komatsu, Bell, or Hitachi trucks, while Pronto learns routes, dispatches trucks from a phone, and handles autonomy on site. That lower friction entry helps Atoms wedge into fleets that would not replace vehicles just to buy autonomy.
  1 sacra 5 pronto 7 komatsu 8 komatsu

This structure points toward more control layer expansion. As Atoms adds more sites, vehicles, and order flows, the software that schedules work, monitors exceptions, and pushes updates should compound faster than the capital heavy layers beneath it. The physical deployments are likely to remain the customer acquisition and defense moat for a growing software and services core.