chore(security): archive the triage proof of concept at a tag - #108
Merged
Conversation
The two-agent pipeline was built to answer whether the loop works. It does, and it has no further job on this repository, so its code, its three workflows and its as-built design leave main and stay reachable at the annotated tag poc/iac-security-triage. The Trivy scan stays active: it is self-contained, and alerts are still worth raising even with nothing to triage them. The test workflow goes with the code, because those suites were the only tests in the repository. CONTEXT-MAP.md and the label vocabulary now say the capability is dormant rather than describing behaviour that no longer happens, and a runbook holds the restore, including the GitHub state the tag cannot carry. Claude-Session: https://claude.ai/code/session_015hX8i6rguJhtY4btLKfRhM
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.
The two-agent IaC security triage pipeline was built to answer whether the loop
works. It does, and it has no further job on this repository, so it leaves
mainand stays reachable at the annotated tag
poc/iac-security-triage(commit7f6856a), which is pushed.Removed from main
security/iac_security/— the whole capability.github/workflows/iac-security-triage.yml,-remediate.yml,-reconcile.yml.github/workflows/tests.yml— those two suites were the only tests in therepository, so the workflow had nothing left to discover
docs/design/iac-security-triage.mdKept active
iac-security-scan.yml. It is self-contained, and alerts are still worth raisingeven with nothing to triage them. That is now the intended state and the runbook
says so.
Documents
CONTEXT-MAP.mdand the label vocabulary indocs/agents/triage-labels.mdnowsay the capability is dormant rather than describing behaviour that no longer
happens.
docs/runbooks/iac-security-triage-restore.mdholds the restore,including the GitHub state the tag cannot carry: the
AI_API_TOKENsecret andthe
ready-for-remediationlabel.The
disabled_manuallystate the three workflows carried lives only in GitHub'sAPI and goes with the files. That is the right outcome — a restore re-adds them
as active and nothing needs re-enabling.
The ADRs are left as written. They are records of decisions at a time, and
ADR-0007 is already superseded.
Verification
Restored all six paths from the tag into a throwaway worktree and ran both
suites: 150 and 230 tests, both OK.
https://claude.ai/code/session_015hX8i6rguJhtY4btLKfRhM