Skip to main content
IronKernel Platform

Tower: Yard Task Operations (YMS)

Yard task list with active/completed/all segmentation.

Problem

Yard task list with active/completed/all segmentation.

Capability

Operates yard-task queues with completion, prioritization, and resilience workflows.

How it works

  1. 1 Yard task list with active/completed/all segmentation.
  2. 2 Priority/status badge rendering and route/location detail.
  3. 3 Task detail workflow with accept/start, complete, and reject actions.
  4. 4 Elapsed timer and completion-note capture.

Operational outcomes

  • Yard task list with active/completed/all segmentation.
  • Priority/status badge rendering and route/location detail.
  • Task detail workflow with accept/start, complete, and reject actions.

Integration boundaries

  • TMS (Primary Runtime Source)
  • CMMS (Embedded Health Context)
  • YMS (Task Execution Context)

Proof model

Feature-level proof

  • Yard Task Operations (YMS) scope is defined in product module catalog.

    verified

    docs/products/tower/product.md · Module Catalog > Yard Task Operations (YMS)

  • Tower driver oversight and cockpit workflows are implemented in dedicated portal pages and hooks.

    verified

    docs/products/tower/product.md · Module Catalog > Driver Cockpit Dashboard

    Code: frontend/apps/portal/src/products/tower/pages

    Contract: proto/tms/loads/v1

  • Tower oversight surfaces are implemented in portal product modules.

    verified

    docs/products/tower/product.md · Module Catalog > Load and Stop Oversight

    Code: frontend/apps/portal/src/products/tower

    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 (0).

This feature is currently not linked to a named solution route. Review this behavior directly, then validate continuity through adjacent solution and feature-map routes.

Continuity routes for this capability

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

This capability is currently mapped in adjacent solution and continuity routes. Browse linked solution routes first, then return here when cross-route continuity is expanded.