Pilot: Vehicle Selection
Provides secure vehicle selection and persistence so driver actions remain correctly tied to the active unit.
Capability
How it works
- 1 Post-authentication flow for truck/unit number selection.
- 2 Session persistence for selected vehicle across app restarts.
- 3 Vehicle dropdown with search and filtering.
Operational outcomes
- Post-authentication flow for truck/unit number selection.
- Session persistence for selected vehicle across app restarts.
- Vehicle dropdown with search and filtering.
Integration boundaries
- TMS
- CMMS
- Crew
Proof model
Feature-level proof
Vehicle Selection scope is defined in product module catalog.
verified
docs/products/pilot/product.md · Module Catalog > Vehicle Selection
Pilot trip workflows and stop progression are implemented in mobile load and stop views.
verified
docs/products/pilot/product.md · Module Catalog > Trip and Stop Management
Code: frontend/apps/mobile/src/pages/Loads.tsx
Contract: proto/tms/loads/v1
Pilot trip and stop workflows are implemented in mobile and load components.
verified
docs/products/pilot/product.md · Module Catalog > Trip and Stop Management
Code: frontend/apps/mobile/src/components/load
Contract: proto/tms/loads/v1
Solution routes that reuse this feature
Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (1).
Field execution continuity
Outcome: Trip and compliance actions remain durable through offline capture and replay.
Field execution remains durable through connectivity gaps when mobile workflows replay deterministically.
Continuity routes for this capability
Route-level continuity checks where this feature appears in product-pair workflows.
Driver-First Execution
Formula: Pilot + TMS
Open continuity routeOperational validation path
Use adjacent feature and solution routes to inspect how this capability participates in cross-product execution.