<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>AI Research on johnmatrix</title>
		<link>https://johnmatrix.org/ai-research/</link>
		<description>Recent content in AI Research on johnmatrix</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 24 Jul 2026 16:08:43 +0100</lastBuildDate>
		
			<atom:link href="https://johnmatrix.org/ai-research/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>20 Concepts That Explain Modern AI</title>
				<link>https://johnmatrix.org/ai-research/20-concepts-that-explain-modern-ai/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/20-concepts-that-explain-modern-ai/</guid>
				<description>&lt;p&gt;Most people who use AI every day cannot explain what is happening when they hit enter&amp;hellip;A lot of senior engineers in Anthropic/OpenAI likely neither! That is fine for using it and a liability for building on it or securing it. These are the twenty concepts that, once they click, turn the whole field from magic into machinery. No maths required, purely the mental models.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Agent Containment Failures in Offensive Tool-Use</title>
				<link>https://johnmatrix.org/ai-research/agent-containment-failures-in-offensive-tool-use/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/agent-containment-failures-in-offensive-tool-use/</guid>
				<description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;When you build an autonomous agent with real offensive capabilities - not a demo, not a CTF solver, but a system designed to find vulnerabilities in production environments - containment isn&amp;rsquo;t optional. It&amp;rsquo;s the primary engineering challenge.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Building an Autonomous Pentest Agent: What I Learned the Hard Way</title>
				<link>https://johnmatrix.org/ai-research/building-an-autonomous-pentest-agent/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/building-an-autonomous-pentest-agent/</guid>
				<description>&lt;p&gt;I spent six months building an autonomous penetration testing agent. Not wrapping Nmap in a ChatGPT prompt. Not asking Claude to &amp;ldquo;hack this website.&amp;rdquo; A real system - 32 detectors, 1,500+ automated tests, engagement database, proof-of-exploit validation, chain analysis. The kind of thing that finds a SQL injection in a path parameter, escalates to UNION-based extraction, dumps the users table, and records machine-verifiable evidence. In under two minutes.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Context Engineering: The Skill Nobody Named in 2024</title>
				<link>https://johnmatrix.org/ai-research/context-engineering/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/context-engineering/</guid>
				<description>&lt;p&gt;Prompt engineering is being quietly demoted. The people building real agentic systems realised the prompt is the small part. The big part is everything &lt;em&gt;around&lt;/em&gt; the model: the briefing docs, the skills, the connectors, the retrieval, the memory, and the way the agent finds exactly what it needs at each step without drowning in what it does not. Prompts still matter. They just aren&amp;rsquo;t the thing that decides whether your agent holds up over a long task.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Credential Sprawl in AI-Assisted Development</title>
				<link>https://johnmatrix.org/ai-research/credential-sprawl-in-ai-assisted-development/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/credential-sprawl-in-ai-assisted-development/</guid>
				<description>&lt;h2 id=&#34;the-problem&#34;&gt;The Problem&lt;/h2&gt;&#xA;&lt;p&gt;I scanned 200 real AI coding sessions and found a median of 8 live secrets each &amp;ndash; AWS keys, SSH private keys, production database URLs &amp;ndash; sitting in plaintext JSONL files that never rotate, never encrypt, and sync to the cloud by default. A single developer&amp;rsquo;s session history over six months averaged 347 unique secrets across all log files.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Graphing the Agent: Orchestration Graphs and the New Control Plane</title>
				<link>https://johnmatrix.org/ai-research/agent-orchestration-graphs/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/agent-orchestration-graphs/</guid>
				<description>&lt;p&gt;&lt;em&gt;How agent systems went from chains to graphs, and why the graph is where containment now lives.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;Every agent you have ever built has a shape, whether or not you drew it. A single prompt is a point. A ReAct loop &amp;ndash; think, act, observe, repeat &amp;ndash; is a circle. A pipeline of planner → researcher → writer is a line. And the moment you add &amp;ldquo;if the tests fail, go back to the coder; if they pass, go to the reviewer; if the reviewer rejects, go back again with the review attached,&amp;rdquo; you have drawn a directed graph with a cycle in it. Most builders never draw that graph on purpose. In 2026, drawing it on purpose is the difference between an agent system you control and one you merely observe. The graph &amp;ndash; nodes as units of work, edges as decisions, state as the thing that flows through both &amp;ndash; has become the control plane of serious agent engineering, and for anyone who thinks about security for a living, it is also where containment now lives or dies.&lt;/p&gt;</description>
			</item>
			<item>
				<title>How LLMs Are Actually Built: The Architecture Is the Part That Matters Least</title>
				<link>https://johnmatrix.org/ai-research/how-llms-are-actually-built/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/how-llms-are-actually-built/</guid>
				<description>&lt;p&gt;If architecture were the moat, everyone would already have a frontier model. The transformer is published, standardised, and freely available &amp;ndash; every major lab uses roughly the same building blocks. Ask most people how you build a model like Claude or GPT and they say &amp;ldquo;transformers,&amp;rdquo; as if the neural network design is the secret. It isn&amp;rsquo;t.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Loop Engineering, 2026: The Bash Loop That Ate Software Development</title>
				<link>https://johnmatrix.org/ai-research/loop-engineering-2026/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/loop-engineering-2026/</guid>
				<description>&lt;p&gt;&lt;em&gt;From Ralph Wiggum to dark factories: what running agents unattended actually costs, how it fails, and the security bill nobody budgets for.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;In July 2025, Geoffrey Huntley published a blog post containing what might be the highest-leverage line of shell ever written:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Loop Engineering: Replacing Yourself as the Prompter (and the Security Tax Nobody Budgets For)</title>
				<link>https://johnmatrix.org/ai-research/loop-engineering/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/loop-engineering/</guid>
				<description>&lt;p&gt;For two years the workflow was: write a prompt, share context, read the output, write the next prompt. The agent was a tool you held the entire time. That phase is ending.&lt;/p&gt;</description>
			</item>
			<item>
				<title>MCP Permission Models Are Broken</title>
				<link>https://johnmatrix.org/ai-research/mcp-permission-models-are-broken/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/mcp-permission-models-are-broken/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve built five open-source MCP servers in Go that give AI agents access to security infrastructure: web proxies (Caido, Burp Suite), EDR platforms (SentinelOne), bug bounty APIs (HackerOne), and SIEM search. Each server required designing a permission model from scratch because MCP doesn&amp;rsquo;t provide one. What I discovered: the protocol has a fundamental authorization gap that makes building safe agent tooling unnecessarily hard.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Offensive AI in Bug Bounty: The Real State of Play</title>
				<link>https://johnmatrix.org/ai-research/offensive-ai-in-bug-bounty/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/offensive-ai-in-bug-bounty/</guid>
				<description>&lt;p&gt;Two things are happening in bug bounty right now, and they point in opposite directions. AI-generated garbage is drowning triage teams and killing open-source programs. At the same time, skilled researchers are quietly using AI to find vulnerabilities that scanners and fuzzers never could. The gap between the two is widening fast.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Prompt Injection and the Agentic Attack Surface</title>
				<link>https://johnmatrix.org/ai-research/prompt-injection-and-the-agentic-attack-surface/</link>
				<pubDate>Fri, 24 Jul 2026 16:08:43 +0100</pubDate>
				<guid>https://johnmatrix.org/ai-research/prompt-injection-and-the-agentic-attack-surface/</guid>
				<description>&lt;p&gt;I test things that break. The interesting thing about LLM security is that the attack surface is fundamentally unlike anything in traditional pentesting, and most people coming from a classic security background get it wrong on the first contact.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
