Fix GPU gating: use operational tightness for capacity expansion#96
Merged
Conversation
Component capacity expansion (both organic growth and discrete expansions) was driven by plan-demand-based tightness, which reflects the unconstrained order book. When GPU gating limits actual deployment to a fraction of plan, non-binding components saw high tightness and expanded aggressively — building capacity that could never ship because deployment was bottlenecked elsewhere. Introduce operationalTightness (from effectiveDemand) for expansion signals: - Organic growth now uses operationalTightness instead of market tightness - Discrete expansion forecasts from effectiveDemand instead of planDemand - Market tightness (planDemand) preserved for price index and reporting The bottleneck component still gets correct expansion signals because its effectiveDemand (~1.5× actual consumption) exceeds its supply, yielding operationalTightness > 1. Non-bottleneck components see low operational tightness (effectiveDemand << potentialSupply) and stop expanding. https://claude.ai/code/session_01J8wXCbNnnMRuXP52e4xtsM
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
2 participants
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.
Component capacity expansion (both organic growth and discrete expansions) was driven by plan-demand-based tightness, which reflects the unconstrained order book. When GPU gating limits actual deployment to a fraction of plan, non-binding components saw high tightness and expanded aggressively — building capacity that could never ship because deployment was bottlenecked elsewhere.
Introduce operationalTightness (from effectiveDemand) for expansion signals:
The bottleneck component still gets correct expansion signals because its effectiveDemand (~1.5× actual consumption) exceeds its supply, yielding operationalTightness > 1. Non-bottleneck components see low operational tightness (effectiveDemand << potentialSupply) and stop expanding.
https://claude.ai/code/session_01J8wXCbNnnMRuXP52e4xtsM