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

Tower: Pilot Mirror and Replay Health

Observes Pilot-replay and manual-review workflows to keep mirror data operationally trustworthy.

Problem

Observes Pilot-replay and manual-review workflows to keep mirror data operationally trustworthy.

Capability

Observes Pilot-replay and manual-review workflows to keep mirror data operationally trustworthy.

How it works

  1. 1 Pilot mirror health page for replay queue depth, DLQ backlog, and intervention-needed queues.
  2. 2 Replay operations support for pending webhook DLQ items from Tower.
  3. 3 Readiness-event feed surfaced for manager-side intervention continuity.
  4. 4 Person-focused drill-down controls for replay ledger, DLQ backlog, manual reviews, and readiness events.

Operational outcomes

  • Pilot mirror health page for replay queue depth, DLQ backlog, and intervention-needed queues.
  • Replay operations support for pending webhook DLQ items from Tower.
  • Readiness-event feed surfaced for manager-side intervention continuity.

Integration boundaries

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

Proof model

Feature-level proof

  • Pilot Mirror and Replay Health scope is defined in product module catalog.

    verified

    docs/products/tower/product.md · Module Catalog > Pilot Mirror and Replay Health

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