Product intelligence: make the FDR regime drive the dashboard, and surface hidden recommendations#367
Draft
Austinw004 wants to merge 2 commits into
Draft
Product intelligence: make the FDR regime drive the dashboard, and surface hidden recommendations#367Austinw004 wants to merge 2 commits into
Austinw004 wants to merge 2 commits into
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
RegimeGuidanceBannermakes the product's thesis operational instead of a corner badge. For the active regime it shows, in plain manufacturing language: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
recommendedActionper 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 rawaiRecommendedActionenum likeurgent_reorderis deliberately not shown — that's developer language.)Verification
npm run buildclean on both commits (Vite + esbuild).mainis 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