Move the triage routing rule into docs/TRIAGE_RULES.md - #121
Open
emmanuelgjr wants to merge 1 commit into
Open
emmanuelgjr wants to merge 1 commit into
emmanuelgjr wants to merge 1 commit into
Conversation
The rule for where an incoming item goes was written down inside evals/EXTERNAL_BENCHMARKS.md, which is the wrong home: it governs the incident index and the close-as-noted path as much as the catalogue, and a reader deciding what to do with a CVE has no reason to look in an evals file. docs/TRIAGE_RULES.md now states it once — the default (note and close), the two exceptions (append as a citation to a real-world failure, catalogue a published benchmark), how CVEs are recorded, and what an agent may decide versus what is reserved. The evals file keeps a one-line pointer rather than a copy, so the two cannot drift apart. GOVERNANCE.md references it from the decision-making section, next to the mapping-dispute path. Text only; no data, schema or tooling changes. Baseline before and after: 0 errors, 88 warnings, 327 passed; 85/85 tests. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Item 6 of the batch. Please do not merge until you have read it — no other changes are in this branch.
Why move it
The routing rule was written inside
evals/EXTERNAL_BENCHMARKS.md(#118). That is the wrong home: the rule governs the incident index and the close-as-noted path at least as much as the catalogue, and someone deciding what to do with an incoming CVE has no reason to look in an evals file.What changed
docs/TRIAGE_RULES.md— the rule stated once: the one-line version (data/incidents.jsonrecords real-world deployment failures, nothing else), the default and its two exceptions, how CVEs are recorded (severity transcribed,basisquoted,confirmed_byempty, weak provenance stated in the record), what happens when an item blends categories or when a rule and its example disagree, and the line between what an agent may route and what stays a human judgment.evals/EXTERNAL_BENCHMARKS.md— the section is moved, not copied: what remains is a one-line pointer, so the two files cannot drift apart.GOVERNANCE.md— references it from Decision-making, beside the mapping-dispute path.Text only. No data, schema, tooling or webapp changes.
Verification
Baseline before and after, identical:
validate.jsnpm run test:scriptsAll four relative links in the new file resolve (
docs/EVIDENCE_METHODOLOGY.md,evals/EXTERNAL_BENCHMARKS.md,GOVERNANCE.md, and the pointer back).🤖 Generated with Claude Code