Skip to content

Run the Axiom parity check on pull requests (warn-only) - #10048

Draft
MaxGhenis wants to merge 2 commits into
mainfrom
axiom-parity-check
Draft

MaxGhenis wants to merge 2 commits into
mainfrom
axiom-parity-check

Conversation

@MaxGhenis

Copy link
Copy Markdown
Contributor

Runs PolicyEngine/.github's reusable Axiom parity check on every PR (PolicyEngine/.github#9).

  • What it does. It verifies the description's axiom: line against GitHub:
    • queued issues must exist, carry pe-parity and be dispatch-ready;
    • encoded PRs must exist and be open or merged;
    • encoded-correct modules and companion tests must exist on rulespec-us main;
    • n/a needs an allowed category.
      It also comments with suggested lines, found by mapping the changed files' reference URLs to Axiom modules and open issues.
  • Warn-only. It reports in the job summary and never fails the job. Enforcing comes later, after a couple of weeks of results.
  • PR template. It now shows the canonical claims: the companion test for encoded-correct, and the category for n/a.

Draft until PolicyEngine/.github#9 merges. The caller points at that PR's branch so this PR exercises the workflow end to end. Before merging, I'll switch it to @main and drop tooling-ref.

axiom: n/a: infra: CI workflow and PR template only

🤖 Generated with Claude Code

MaxGhenis and others added 2 commits October 10, 2026 07:19
Calls PolicyEngine/.github's reusable axiom-parity workflow, which verifies
the PR description's axiom: line and comments with suggested lines. It
reports and never blocks while in warn mode. The PR template now shows the
canonical claims, including the companion test and the n/a category.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…til it merges

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

1 participant