Skip to main content
IronKernel Platform

Pilot: Compliance and Readiness (Crew-Linked)

Tracks readiness blockers and onboarding/credential health through Crew-linked compliance workflows.

Problem

Tracks readiness blockers and onboarding/credential health through Crew-linked compliance workflows.

Capability

Tracks readiness blockers and onboarding/credential health through Crew-linked compliance workflows.

How it works

  1. 1 Credential onboarding experience with consent-aware submission behavior.
  2. 2 Compliance renewal inbox with urgency/status grouping.
  3. 3 Required-action normalization and deterministic prioritization.
  4. 4 Readiness blockers with remediation hints and decision-case context.

Operational outcomes

  • Credential onboarding experience with consent-aware submission behavior.
  • Compliance renewal inbox with urgency/status grouping.
  • Required-action normalization and deterministic prioritization.

Integration boundaries

  • TMS
  • CMMS
  • Crew

Proof model

Feature-level proof

  • Compliance and Readiness (Crew-Linked) scope is defined in product module catalog.

    verified

    docs/products/pilot/product.md · Module Catalog > Compliance and Readiness (Crew-Linked)

  • 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.