Droid Control Automate terminals and browsers. Three routing decisions, then atoms guide you the rest of the way. Ground rules 1. Real apps, real environments. Non-deterministic behavior (LLM responses, network latency, variable output) is expected. Handle it with / . Never substitute fixtures or mocked data. 2. Commit to execution. Once you've chosen a driver, run the plan. If something fails mid-run, recover and retry -- don't re-evaluate the approach. 3. Atoms are self-contained. Load one and follow its mechanics. No cross-referencing needed. 4. is the ONLY way to launch recorded sessions.…