Add reform impacts dashboard planning doc (#806)#1732
Open
vahid-ahmadi wants to merge 1 commit into
Open
Conversation
#806 asks for a dashboard tracking high-importance reform budgetary impacts over time and across model / data versions. Auditing the existing infrastructure: - reforms_config.yaml already has 9 canonical regression fixtures (basic rate +1pp, UC taper to 20%, VAT +2pp, etc.) with expected impacts and tolerances. - test_parametric_reform_impacts.py runs each fixture in CI and fails on drift outside the tolerance. So the *fixtures* exist; what's missing is a published *time series* view onto them. The page proposes: - append-only CSV / Parquet storage of (timestamp, policyengine_uk_version, policyengine_uk_data_version, dataset_url, reform_name, expected_impact, observed_impact, gap), - a scheduled GitHub Actions runner (weekly + on tag) walking reforms_config.yaml, - three publication paths in order of effort: docs page Plotly chart, living JSON endpoint, policyengine.org dashboard tile, - annotations for EFO releases, dataset refreshes, methodology PRs. Cross-links to the nowcasting comparison and child poverty validation pages so the three together form a coherent "how is the model doing" view.
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
tests/microsimulation/reforms_config.yamlhas 9 canonical regression entries (basic-rate +1pp, UC taper to 20%, VAT +2pp, etc.) with expected impacts and tolerances, andtest_parametric_reform_impacts.pyexercises them on every PR. What's missing is a time series view onto them.docs/book/validation/reform-impacts-dashboard-plan.mdproposes:(timestamp, version, dataset, reform_name, expected_impact, observed_impact, gap)rows on a CSV / Parquet (HuggingFace dataset orgh-pagesartefact);reforms_config.yaml;Test plan
validation/.🤖 Generated with Claude Code