DDC PR Proof
Semantic proof-of-change for pull requests. Identify changes in behaviour, authority, failure semantics, assumptions, and guarantees that may not be obvious from the code diff.
What it does
DDC PR Proof is a local-first semantic proof-of-change layer for GitHub pull requests.
Traditional code review tells you which lines changed. Generic AI reviewers can summarize code or suggest improvements. DDC PR Proof focuses on a different question: What did this pull request actually change in behaviour, risk, authority, and assumptions?
PR Proof compares the stated purpose of a pull request with the material consequences visible in its diff and repository evidence. It examines behaviour changes, configuration changes, dependencies, permissions, authority, retry semantics, recovery, rollback, failure modes, tests, missing test evidence, documentation, and declared guarantees.
Every run can produce a deterministic machine-readable proof artifact and proof hash. Current evidence-backed indicators include DDC Surprise Score, Intent Alignment, Merge Posture, behaviour changes, authority changes, failure-mode changes, test-surface evidence, and supporting evidence for each finding. These are deterministic heuristics derived from observable evidence, not probabilistic claims of truth.
The current Action runs inside GitHub's workflow environment and does not require source code to be sent to an external LLM or hosted DDC service. DDC PR Proof is deliberately not another generic AI code reviewer. Its purpose is to expose semantic surprise between what a pull request claims to change and what it materially changes.
Who it helps
Software engineering teams, maintainers, security reviewers, open-source projects, platform teams, and organizations reviewing consequential code changes.