Skip to main content
IronKernel
Products Solutions For Customers About FAQ Contact
IronKernel Platform

Pilot: Notifications

Routes operational alerts across high-signal events with preference-aware delivery and deep-link consistency.

Problem

Routes operational alerts across high-signal events with preference-aware delivery and deep-link consistency.

Capability

Routes operational alerts across high-signal events with preference-aware delivery and deep-link consistency.

How it works

  1. 1 Device registration and preference-aware notification behavior.
  2. 2 HOS, settlement, reefer, and urgent-task routing into in-app context.
  3. 3 Configurable warning thresholds and deep-link behavior.
  4. 4 Event-consumption parity for cross-product driver notifications.

Operational outcomes

  • Device registration and preference-aware notification behavior.
  • HOS, settlement, reefer, and urgent-task routing into in-app context.
  • Configurable warning thresholds and deep-link behavior.

Integration boundaries

  • TMS
  • CMMS
  • Crew

Proof model

Feature-level proof

  • Notifications scope is defined in product module catalog.

    verified

    docs/products/pilot/product.md · Module Catalog > Notifications

  • 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

Continuity routes for this capability

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