predictive control tower quality gates + SHAP evidence review-ready handoff

Verification continuity

The Logistics Prophet

Predictive logistics control tower for teams that need runtime posture, recovery proof, explainability, and operator handoff to read as one walkthrough.

  • Actionable risk queue with owner / ETA workflow and downstream handoff guardrails
  • Recovery drill proof that compares baseline risk against the proposed operator plan
  • Evidence bundle that ties SHAP, governance, and postmortem-ready exports together
Public site = status map

This public surface summarizes the proof route and copyable output artifacts. It does not pretend to be the live runtime; the runtime evidence lives in the app and service-health payloads.

More copy actions

Fast path: start with the checklist, then copy routes. Open More copy actions only when you need a claim block or the full bundle. Keyboard: R routes · C claim · B bundle · K checklist · ? help.

One-lane continuity

Hold one risky lane from baseline through handoff.

Pick the lane you want to narrate, then keep its proof route and next action visible without jumping around the page.

Baseline risk is still the anchor.

Route: /healthz → /api/runtime/brief → /api/runtime/scorecard

Next move: confirm the lane still needs intervention.

Proof: runtime posture, queue signal, and watchouts stay together first.

Copyable lane note

Use Copy Lane Note once the lane story is concise enough to forward.

Lane focus starts on baseline risk so the recovery story has context.

Lane continuity stays blocked until owner, ETA, and proof route all match the same lane.

Proof freshness matters: rerun health and review-pack export before forwarding stale lane copy.

Fresh route: /healthz → /api/runtime/brief → /api/review-pack → evidence pack export.

01 · Runtime posture

Confirm service health and current watchouts before reading queue claims.

02 · Evidence

Use quality gates, recovery deltas, and SHAP before claiming actionability.

03 · Handoff

End with the summary bundle and export bundle once the story is reviewable.

Recovery proof route

  1. /healthz confirms posture and links the compact reviewer snapshot.
  2. /api/runtime/brief and /api/runtime/scorecard frame model and audit readiness.
  3. The recovery drill summary compares baseline queue risk against the proposed operator plan.

Why SHAP is paired with actionability

  • SHAP explains why the shipment or lane is risky.
  • Quality gates and semantic evidence show the explanation is grounded.
  • Owner / ETA workflow proves the recommendation can be acted on before handoff.

Honest public-site contract

The public site is a user-facing summary and routing aid. It mirrors the runtime proof sequence, but it does not claim that the static page is the operational console itself.

Use the README walkthrough and summary bundle export when forwarding the story outside the product team.

What to show once one risky lane is selected

01 · Baseline risk

Start with the pre-recovery posture so the reviewer sees why this lane needs intervention at all.

02 · Recovery delta

Use the recovery drill and SHAP evidence together, so “why this works” and “what changed” stay connected.

03 · Review-ready handoff

Finish with the summary bundle and export path once owner, ETA, and postmortem posture all agree.

Review Signals

  • Clear purpose and original content
  • Recovery / explainability / handoff continuity instead of isolated feature bullets
  • Public policy / contact / compliance pages plus crawlable site artifacts

Public-site note

This public site stays lightweight on purpose. Ads remain disabled until a real publisher ID and slot are configured.