Skip to content

Document post-CTR council tax calibration path#387

Draft
MaxGhenis wants to merge 2 commits intomainfrom
codex/post-ctr-council-tax-calibration
Draft

Document post-CTR council tax calibration path#387
MaxGhenis wants to merge 2 commits intomainfrom
codex/post-ctr-council-tax-calibration

Conversation

@MaxGhenis
Copy link
Copy Markdown
Contributor

Summary

This is a contingent draft for the data side of the post-CTR Council Tax pipeline. It documents the switch path from FRS-derived Council Tax/CTB signals toward structural gross Council Tax minus modelled CTR, without changing any production calibration behavior.

Changes:

  • Adds docs/post_ctr_council_tax_calibration.md describing the current CT calibration state, the target post-CTR pipeline, and acceptance gates before switching.
  • Adds the new page to the MyST docs table of contents.

Dependency

Blocked on PolicyEngine/policyengine-uk#1534 completing UK-wide CTR coverage. It should also follow the semantics scaffold in PolicyEngine/policyengine-uk#1657.

Validation

  • uv run python -c "from pathlib import Path; import yaml; yaml.safe_load(Path('docs/myst.yml').read_text()); assert Path('docs/post_ctr_council_tax_calibration.md').exists()"

Note: uv run briefly resolved the local environment and changed uv.lock; that unrelated lockfile churn was removed before commit. The local commit hook also failed because this new worktree has no bd database, so the docs commit was made with --no-verify after the YAML validation above.

@vahid-ahmadi
Copy link
Copy Markdown
Collaborator

Approve as a draft. Three small asks:

  1. Lowercase the H1 to match the project's sentence-case convention.
  2. Use full URLs for the policyengine-uk#1534 / #1657 references so MyST renders them as cross-repo links.
  3. Confirm with docs-owner that the user-facing docs site is the right venue, vs. an internal RFC/decisions folder.

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