Skip to content

Product intelligence: make the FDR regime drive the dashboard, and surface hidden recommendations#367

Draft
Austinw004 wants to merge 2 commits into
mainfrom
claude/youthful-keller-YVpha
Draft

Product intelligence: make the FDR regime drive the dashboard, and surface hidden recommendations#367
Austinw004 wants to merge 2 commits into
mainfrom
claude/youthful-keller-YVpha

Conversation

@Austinw004

Copy link
Copy Markdown
Owner

What customers experience now

This turns two dashboard surfaces from descriptive into prescriptive — the difference between a dashboard and a command center.

1. The FDR regime now drives the command center

New RegimeGuidanceBanner makes the product's thesis operational instead of a corner badge. For the active regime it shows, in plain manufacturing language:

  • What it means for procurement (no economist jargon)
  • Cost outlook (e.g. Asset-Led Growth → "Costs likely rising 8–12% this quarter")
  • What to do now — a specific, prescriptive action set (lock contracts / defer / build safety stock on single-source only / secure supply ahead of price moves)
  • "Why this guidance?" — an expandable reasoning disclosure, tagged as decision guidance (not a measured outcome)
  • A direct action path — primary + secondary buttons routing to procurement / supplier-risk / scenario-planning / forecasting

It carries a regime-aware accent (calm emerald → amber heating up → red tension → opportunity sky) so the customer builds unconscious market awareness, and a recent-shift flag ("Regime shifted to X today — your procurement posture has changed") surfaces a regime change as an event using the API's regimeDurationDays.

Wired prominently after the dashboard hero and into the empty state, so a trial user sees the model working with a concrete play on first login — before any data is loaded.

2. Materials at Risk now tells you what to do

The stockout-alerts API already computed a friendly, EOQ-aware recommendedAction per material — the widget just never rendered it. Customers saw the risk without the prescription. Each at-risk row now shows "Recommended: <action>" plus the economic order quantity when an AI optimization exists. (The raw aiRecommendedAction enum like urgent_reorder is deliberately not shown — that's developer language.)

Verification

  • npm run build clean on both commits (Vite + esbuild).
  • New component is self-contained; all referenced routes exist in the router; Tailwind accent classes written as full literal strings (JIT-safe).
  • Not deployed — branch only; production main is untouched.

Follow-ups (not in this PR — need design input)

Broader product-intelligence work to extend the same principle: regime-aware tone across all dashboard widgets, forecast pages stating recommended actions + confidence intervals + regime linkage, and supplier/material detail pages as connected "intelligence dossiers."

https://claude.ai/code/session_01V61MwiSuV5uDemytaChzZC


Generated by Claude Code

claude added 2 commits June 5, 2026 08:09
Make the FDR regime model drive the experience instead of being a corner
badge. New RegimeGuidanceBanner translates the active regime into plain
manufacturing language, a prescriptive "what to do now" action set, the
expected cost outlook, a "Why this guidance?" reasoning disclosure, and a
direct action path (primary + secondary buttons routing to procurement /
supplier-risk / scenario-planning / forecasting). Regime-aware accent tone
(calm emerald -> amber heating up -> red tension -> opportunity sky) builds
unconscious awareness, and a recent-shift flag surfaces a regime change as an
event. Wired prominently after the dashboard hero and into the empty state so
trial users see the model working on first login.

Co-Authored-By: Claude <noreply@anthropic.com>
The stockout-alerts API already returns a friendly, EOQ-aware recommendedAction
sentence per material, but the widget never rendered it — customers saw the risk
without the prescription. Now each at-risk row shows "Recommended: <action>"
(plus the economic order quantity when an AI optimization exists). The raw
aiRecommendedAction enum ("urgent_reorder", etc.) is deliberately not shown.

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants