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

Tower: Decision Provenance and Drill Controls

Adds decision provenance and drill controls for post-hoc investigation and operational simulation.

Problem

Post-incident review is inconsistent when decision context and drill-mode boundaries are not explicit.

Capability

Adds decision provenance and drill controls for post-hoc investigation and operational simulation.

How it works

  1. 1 Cross-product decision provenance panel added to driver cockpit and dedicated route (Crew/TMS/CMMS gate trace).
  2. 2 Drill mode and simulated-only controls added to Tower runtime with persisted operator preference.
  3. 3 Provenance badges and drill filtering added across loads, load stops, messages, and yard tasks.
  4. 4 Canonical provenance parsing now consumes explicit metadata fields (provenance / source_provenance / simulation booleans) instead of...

Operational outcomes

  • Stronger operator trust through transparent decision provenance.
  • Safer simulation and drill operations without mixing live and drill states.

Integration boundaries

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

Proof model

Feature-level proof

  • Decision Provenance and Drill Controls scope is defined in product module catalog.

    verified

    docs/products/tower/product.md · Module Catalog > Decision Provenance and Simulation Drill Controls

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