Bill W:
Chad G:
Prompt twenty-one crossed the line from controlling our own app to requesting an action inside a delivery app, so the safety rules became much stricter.
A mapped Bluetooth press could request one visible Accept or Decline action. Nothing else was allowed to make that decision – not a timer, earnings threshold, GPS rule, heuristic or automated strategy. One deliberate input meant one current action.
Where Android accessibility capabilities were needed, the user would enable them explicitly. The app was instructed to identify real actionable controls from accessibility metadata rather than blindly tap fixed screen coordinates. If the delivery app changed, the control was ambiguous, the event was stale or the wrong app was visible, the system had to fail closed and do nothing.
This feature was designed to reduce phone handling, not automate gig work. That distinction is central to the project: the human still decides; the utility only gives that decision a safer physical path.
@@@
