Skip to content

Add aiArch red-teaming workflow to Recommended Reading - #31

Merged
requie merged 1 commit into
requie:mainfrom
sofus-common:add-aiarch-red-teaming-workflow
Oct 11, 2026
Merged

requie merged 1 commit into
requie:mainfrom
sofus-common:add-aiarch-red-teaming-workflow

Conversation

@sofus-common

Copy link
Copy Markdown
Contributor

Adds one practitioner workflow to Blogs and Articles, Recommended Reading.

Disclosure: I wrote this and run the site it is on (aiArch), so it is first-party. I have marked it "vendor-described" in the entry. If you prefer, I can also add a row for it to resources-validation.md with that tag, matching how #29 handled a vendor-published source.

What it adds: a repeatable practice rather than a taxonomy (map the attack surface against the named categories, build the automated adversarial suite, decide which surfaces you can reach, run it per release and on a schedule, triage findings back into guardrails and evals), plus two as-built failures from the author's own stack: a red-team fixture that passed by testing nothing, and a safety policy that was blocked by the gateway's own guardrails.

The entry is one line, English README.md only, no translation changes. Happy to move it or shorten the description.

@requie
requie merged commit 0b55274 into requie:main Oct 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants