Start at the hero, then scroll toward the workflow animation.
“This is Max’s public dashboard. The landing page shows the complete mission loop—from the original request, through marketplace search and Prava approval, to delivery tracking and the robot handoff.”
Pause briefly on the animated Ask → Shop → Approve → Bring it back sequence.
Open Live mission.
“The Live Mission page reads directly from our deployed backend. It combines robot camera and location availability, the selected product, exact quote, payment state, and every safe mission event.”
Point at the event feed:
“Here, OpenAI understood the request, Swiggy returned the quote, Prava created the approval session, and the owner approved that exact amount. Addresses, credentials, and control access are intentionally excluded from the public feed.”
If the Pi can be online during recording, do that. Otherwise move past the waiting camera/GPS cards quickly.
Open History, then expand the declined mission.
“Every mission is persisted with its complete timeline. We can inspect the commerce, payment, checkout, and fulfilment states individually.”
Scroll through the expanded events.
“Failures are recorded too. A declined or cancelled payment stops the workflow cleanly instead of being retried or presented as a successful order.”
This is especially useful Prava proof.
Open ONDC sandbox, show the offer graphic, then scroll to the protocol workbench.
“The commerce layer is not restricted to one marketplace. Swiggy Instamart is our live path, while ONDC demonstrates discovery across multiple sellers through search, select, init, confirm, and status.”
Point at the owner boundary:
“Whichever commerce path is used, it rejoins the same Prava approval and mission record.”
Return briefly to the Live page or the landing-page handoff section.
“When the order reaches campus, the same mission continues into the physical handoff.”
Cut immediately to your friend’s robot footage.