Repository navigation
Conversation
The conclusion used the antithesis construct the paradigm-shift check and the blog-review job flag as an LLM tell. Same meaning, stated directly; matches the wording already used in the LinkedIn post. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JoTNmbmc8o4TJDUGG2gd3P
This branch has not been deployed
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.
One-sentence edit to the conclusion of https://rivassec.com/iam-blast-radius-github-action.html.
Before: "It does not promise that every passing policy is safe, and it cannot guarantee that every risky change is detected. It promises something narrower and more useful: ..."
After: "The promise is deliberately narrow: an enforceable, auditable check that names potential permission risk during review, and refuses to approve what it could not analyze. It does not certify that a passing policy is safe, or that every risky change gets caught."
Why: the old wording is the "not X, it is Y" antithesis that the blog-review job flagged (high confidence) and that reads as an LLM tell in a conclusion. The new wording matches the LinkedIn post.
Modifiedbumped to 2026-10-10.Local checks: em dashes, section dividers, descriptions pass; paradigm-shift now reports only the deliberate opener line it reported before. Anchor and link-graph checks need a full build and run in CI.
🤖 Generated with Claude Code
https://claude.ai/code/session_01JoTNmbmc8o4TJDUGG2gd3P