Repository navigation
Rebuild pricing pipeline with leakage-safe demand modeling and scenario analysis - #1
Merged
Merged
Conversation
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.
Summary
This PR substantially rebuilds the dynamic pricing project around a more defensible modeling architecture.
The previous implementation estimated observational price elasticity and used it directly for price optimization. That approach has been retired. The updated system separates predictive modeling from pricing assumptions:
Key changes
Validation
Current local validation:
pip checkclean/healthreturned 200 with production models loadedgit diff --check origin/main...HEADcleanModeling boundary
The system does not claim to estimate causal price elasticity from observational Airbnb data.
Calendar unavailability is treated as a demand proxy, and pricing outputs are conditional scenario results under explicitly stated sensitivity assumptions. Revenue values are therefore scenario-based proxies rather than claims about realized causal revenue uplift.