Skip to content

Diff-aware claim impact in dtc risk (v0.4.0)#23

Merged
Shakargy merged 1 commit into
mainfrom
v0.4.0-diff-claim-impact
Jul 10, 2026
Merged

Diff-aware claim impact in dtc risk (v0.4.0)#23
Shakargy merged 1 commit into
mainfrom
v0.4.0-diff-claim-impact

Conversation

@Shakargy

Copy link
Copy Markdown
Owner

Summary

Connects the verification layer to the risk layer: a diff should tell you which verified claims it destabilizes.

Claim impact:
  - billing-webhook-signature (previous status: SUPPORTED)
      changed evidence: src/billing/stripe-webhook.ts
      re-verify: dtc verify billing-webhook-signature
  • claims_affected_by_paths intersects diff paths with stored verification evidence fingerprints
  • Only evidence files count - unrelated diffs never flag a claim
  • Silent when nothing is affected (advisory, never noisy)
  • Names the exact changed evidence and the exact re-verify command

Verification

  • 129 tests passing (3 new)
  • E2E verified with a real git diff on the demo repo: touching the webhook handler after verification produces the claim impact section; unrelated changes produce nothing
  • No breaking changes; build + twine clean

Version 0.4.0. No tag, no publish - awaiting approval.

dtc risk --diff now reports which verified claims the diff destabilizes:
previous status, the exact changed evidence files, and the re-verify command.

- claims_affected_by_paths: intersects diff paths with each stored
  verification's evidence fingerprints. Only evidence files count; unrelated
  diffs never flag a claim; silent when nothing is affected.
- Connects the verification layer to the risk layer: concept-level review says
  "this change class needs review", claim impact says "this specific verified
  claim may no longer hold".

129 tests (3 new). No breaking changes. Version 0.4.0.
@Shakargy Shakargy merged commit 4f5ab11 into main Jul 10, 2026
4 checks passed
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