Gatekeeper turns any patch into a reviewable chain of evidence: risk signals, adversarial probes, and a tamper-evident release receipt.
1 trust boundary change requires human review.
The changed token path does not visibly bind issuer, audience, or algorithm policy. A syntactically valid token may be treated as trusted.
const session = jwt.verify(token);The new path derives privilege from request data. An attacker can self-assign authority before the protected action runs.
const role = req.body.role || session.role;The patch changes test execution controls, which can hide regressions while leaving the suite apparently green.
it.skip("rejects member role escalation", async () => {“AI should not lower the bar for trust.
It should make the evidence impossible to ignore.”
Understand exactly what moved, where, and how far the effects can travel.
Turn intended behavior into hostile, executable verification paths.
Export a deterministic receipt that reviewers can reproduce and audit.