Repository navigation
docs: delete the Praxen triage table — issues are the tracker - #94
Merged
Merged
Conversation
Every finding from the 2026-08-12 scan is now a GitHub issue (#6, #71, #82, #86, #88-#93, plus 001/007/009 fixed in 0.7.0), so the in-repo table was a second copy of status with nothing to add. It had already drifted, which is the argument: nine of thirteen rows still read 'awaiting triage' after several had been fixed or filed. Status in two places diverges — the same failure mode this repo has now found three times in its own docs. What is deliberately kept: the dated artifacts under results/ remain the authoritative record of what was found (severity, evidence, file:line citations) and are never edited after the fact, which is what CONTRIBUTING's release-gate rule actually asks for. The gate verdict and RAISE posture stay on the page as the scan's headline. Traceability preserved before deleting: every finding ID now appears in its issue, so PRAX-2026-08-12-0NN stays searchable. Four issues (#82, #86, #88, and #6) did not name their ID and were tagged first — deleting the table before that would have severed the link between a finding and its issue. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Steve Wilson <steve.wilson@exabeam.com>
virtualsteve-exa
force-pushed
the
docs/praxen-triage-index
branch
from
August 13, 2026 21:24
751225e to
ff7f049
Compare
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
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.
The triage table is gone. Every finding from the 2026-08-12 scan is a GitHub issue now, so the in-repo table was a second copy of status with nothing to add.
Why deleting beats maintaining
It had already drifted, which is the whole argument: nine of thirteen rows still read "awaiting triage" after several had been fixed or filed. Status held in two places diverges — the same failure mode this repo has found three times in its own docs during the last day alone (stale paths after the restructure, a fail-open description that contradicted the shipped code, an audit artifact labelled with the wrong version).
What is deliberately kept
The page still carries the scan's headline and gate verdict — 0 Critical, RAISE 2.45/5, remit coverage, the independent-audit line, and the determination that this scan is 0.7.0's gate artifact. And the dated artifacts under
results/are untouched: they remain the authoritative record of what was found — severity, evidence,file:linecitations — and are never edited after the fact. That is whatCONTRIBUTING.md's release-gate rule actually asks for ("a dated artifact… so a reader can tell which release was actually verified"). The table was never the evidence; it was an index over it.In its place is a short pointer: search the tracker for a finding ID, e.g.
PRAX-2026-08-12-004.Traceability was preserved before deleting
That pointer only works if the issues name their finding IDs, and four did not — #82, #86, #88 and #6. I tagged those with their IDs first. Deleting the table before that would have severed the only link between a finding and the issue tracking it, which is the one thing the table held that nothing else did.
All thirteen findings are now searchable by ID:
Verification
Docs-only, one file, −33/+11. No dangling references to the removed section or its anchor anywhere in the repo, every relative link in the file resolves, 268 tests pass, AI BOM current.
🤖 Generated with Claude Code