Release decisions

Approvals have not been recorded in this plan. Each decision below needs an owner and recorded approval before public delivery bookings. The roadmap gates in Roadmap stay closed until these are settled.

Use this page as the client feedback checklist. Every item needs a named approver — commercial, legal, or operations — before launch.

Related: Roadmap · Business requirements · Delivery · Platform

1. Launch city and partners

• Which US service area and first route will pilot point handoff, and which route will prove driver collection second.
• Which organization operates each pilot route, with participating locations and receiving venues confirmed.
• Launch location data delivered and verified: addresses, hours, eligibility, and capacity.
• A US support number staffed for pilot operations.

2. Proof and custody

• Who accepts each physical handoff — location staff, courier, recipient — and which proof is mandatory at each step (tag, claim or PIN check, photo).
• Exception and recovery rules: customer absent, venue closed, bag-count mismatch, lost connectivity. No silent success; every gap produces an explicit recovery or exception state.
• Proof privacy: who may view photos and addresses, for how long, and under what retention and deletion schedule.
• Confirmation that customer tracking means auditable milestones and promised windows — no live GPS or arrival-time claims.

3. Commercial terms

• Delivery quote rules: what sets the price for each route, bag count, and window, and how long a quote stays valid.
• Cancellation and refund policy in writing, including how credits trace back to the paid order.
• Organization settlement: how delivery revenue reconciles to paid orders without changing storage payment behavior.
• Courier compensation: who pays couriers and how it is recorded. Automated courier payouts are outside the first release.
• Loss, damage, and prohibited-items terms, plus insurance position stated plainly — no inherited or implied coverage.

4. Service policies

• Service area boundaries, operating hours, and promised handoff windows.
• Prohibited items, packaging expectations, and maximum liability stated in customer-facing terms.
• Privacy retention for contact details, addresses, and proof photos.
• Partner and driver obligations: custody duties, conduct, and what happens when a handoff fails.
• Support path: how travelers, staff, and couriers reach help during a live job.

5. App-store and payment enablement

• US Stripe account with mobile-pay merchant enablement completed.
• Apple Developer membership and Google Play registration in place.
• Maps keys and billing for both mobile platforms.
• Hosting and backend account ownership transferred, with production secrets for scheduled jobs configured.
• Release configuration, project records, and build secrets for the traveler app and the proposed courier app.

Approval record

Decision group	Owner	Approved
Launch city and partners	Not assigned	Pending
Proof and custody	Not assigned	Pending
Commercial terms	Not assigned	Pending
Service policies	Not assigned	Pending
App-store and payment enablement	Not assigned	Pending

Public delivery bookings start only when every row reads approved, the Phase 5 settlement gate in Roadmap reconciles, and legal and commercial owners sign the US service terms.