docs: add patch deferral revalidation gates#1402
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6133d618e1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | CVE ID | Exception ID | Last Revalidated | Trigger Checked | Current Finding | Required Action | Next Revalidation | | ||
| |---|---|---|---|---|---|---| | ||
| | [CVE-ID] | [EXC-ID/N/A] | [date] | [Patch/KEV/EPSS/Exploit/Exposure/Control] | [Finding] | [Maintain/Escalate/Schedule/Expire/Re-test] | [date] | |
There was a problem hiding this comment.
Include the revalidation owner in the exact output table
When a deferred item has no material change, the new validation fixture requires the report to record the owner, and the trigger list also calls out owner accountability at 50% duration, but this exact output table has no Owner column. Agents following the required format can satisfy the table while omitting who owns the next revalidation, undermining the accountability gate this change adds.
Useful? React with 👍 / 👎.
Created from review issue: #1401
Summary
patch-prioritizationValidation
git diff --check