# grubhub.com / food_local.order_pickup_delivery

Health: degraded
AES: 66
Confidence: low 0.28
Freshness: 0d

## Recipe

Status: active
URI: recipe://grubhub.com/food_local.order_pickup_delivery/public-preflight-v1

1. Open the documented public path for Grubhub: Official public order, menu, delivery, pickup, or help page -> identify location/address/menu/order context and availability cues; stop before cart mutation, account sign-in, payment, place order, support chat, cancellation, or refund submission.
2. Check the listed blockers and policy constraints before entering account, payment, booking, or cancellation state.
3. Stop before any irreversible or user-sensitive action and ask for explicit approval.

## Human Approval

Keep the user present for authentication. Do not request, store, or replay credentials or one-time codes.

## Do Not Cross

- Do not place orders, alter active carts, submit support claims, open chats, cancel orders, or enter payment during public collection.
- Require user-present address, account, order receipt, and final approval for any live pickup, delivery, refund, or cancellation canary.

## Success Signals

- Official ordering or delivery surface identified
- Location/menu/availability checkpoint identified
- Future canary should capture fees, ETA/window, order status, or confirmation email without guessing

## Blockers

- login_required
- human_handoff_required
- dynamic_dom_unstable

## Recommended Actions

- Do not place orders, alter active carts, submit support claims, open chats, cancel orders, or enter payment during public collection. Keeps the agent inside documented, reversible, user-approved boundaries.
- Capture handoff evidence and pause before accepting retention offers. Keeps user intent explicit during adversarial cancellation flows.