For editors, publishers, and technical teams
AI security, working tools, and writing that gets into the mechanism.
Discuss a project on LinkedIn →For the assignment desk
Research features, technical reports, and methods tested against the work itself. Read a piece, inspect the supporting code, or commission the next investigation.
Reviewing code with a system of agents that vote on a verdict is becoming common. The question worth asking is where that kind of reviewer goes blind, and what walks straight through the gap. So I built a small one, then spent most of my time attacking it.
Discuss this piece on LinkedIn →A second redacted-format engagement report: how a safety-detection pipeline's own pattern-loading bug made it match zero inputs, ever, how the fix was verified, and how a later regression-test repair separated broken fixtures from broken HTTP mocks.
Discuss this piece on LinkedIn →A recorded 104-article pass returned 98 files without deterministic flags. A later recheck covers 122 articles. The counts measure regex and age rules, with historical model mentions among the candidates that still need a human read.
Discuss this piece on LinkedIn →Technical features, documentation, reproduction guides, and research reports. Bring a subject, a reader, and a deadline. The work can begin with an existing investigation or a new brief.
Read a research feature →License an existing piece, adapt it for your publication, or commission a follow-up. Permissions and terms are agreed individually before publication.
Include the piece you have in mind, your publication, language, territory, format, and desired publication date. We can discuss a licensed reprint, an adaptation, or a new assignment. Credit, links, edits, exclusivity, fee, and usage period are agreed for the specific use.
Images, screenshots, and code require their own permissions review. Article permission does not automatically include visual assets or third-party material, and code remains subject to its repository license. Supporting links above are sources to inspect, not a bundle of licensed assets.
Technical claims and versions are reviewed again for the proposed publication date. The dates above identify the original pieces.
Discuss republication on LinkedIn →The RSS feed makes new pieces easy to follow. Feed access does not grant republication rights.
Discuss a clearly labeled placement supporting the publication. Sponsorship does not buy coverage, conclusions, or editorial approval. Placement, duration, current audience figures, and terms are agreed for each sponsorship.
Discuss sponsorship →Frontier-model testing, agentic trust boundaries, and security tooling. Scope and deliverables are agreed for each engagement.
MDRN Red Team Sec ↗