IronKernel Platform

Pilot: Yard Operations

Coordinates yard task execution, issue reporting, and mule handoff flow for mobile operators.

Problem

Coordinates yard task execution, issue reporting, and mule handoff flow for mobile operators.

Coordinates yard task execution, issue reporting, and mule handoff flow for mobile operators.

1 Yard task queue and detail workflows with accept/start/complete/reject/cancel actions.
2 Urgent task handling from notification entry points.
3 Yard map mode with cached behavior and stale-state signaling.
4 Field issue quick actions with photo-first reporting flow.

Yard task queue and detail workflows with accept/start/complete/reject/cancel actions.
Urgent task handling from notification entry points.
Yard map mode with cached behavior and stale-state signaling.

Feature-level proof

Yard Operations scope is defined in product module catalog.
verified
docs/products/pilot/product.md · Module Catalog > Yard Operations
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

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.

Route-level continuity checks where this feature appears in product-pair workflows.

Driver-First Execution

Formula: Pilot + TMS

Use adjacent feature and solution routes to inspect how this capability participates in cross-product execution.