Repository navigation
Pinned corpus - what does the integrity check verify? #6
Answered
by
bitforth
camillejackson
asked this question in
Q&A
|
We keep the corpus in the repo and it changed once without anyone noticing, which silently moved our per-class rates. What does the pinning actually verify, and when should we re-pin? |
Answered by
bitforth
Sep 26, 2026
Replies: 1 comment
|
The integrity check records the corpus hash with every run and treats a mismatch against the pinned hash as a usage error, not a silent comparison. Re-pin only when the corpus change is intentional: review the added or edited probes, update the pinned hash in the same commit, and rerun both guards so the per-class deltas are computed on the same corpus. That is what makes a delta between two runs a real guard change. |
0 replies
Answer selected by
camillejackson
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The integrity check records the corpus hash with every run and treats a mismatch against the pinned hash as a usage error, not a silent comparison. Re-pin only when the corpus change is intentional: review the added or edited probes, update the pinned hash in the same commit, and rerun both guards so the per-class deltas are computed on the same corpus. That is what makes a delta between two runs a real guard change.