Injectionator
Build notes and evidence
These published accounts explain the work behind Injectionator. They are selected records, not a complete release history or a claim that historical tools remain available.
Probes and application paths
Probe and MCP: reading the available evidence explains the relationship between test inputs, tool calls and observed effects, with links to the surviving accounts.
Making attribution honest
The demo was lying describes why a blocked request alone does not show which inspector worked, and how probe coverage became a prerequisite for an inspector.
Reading a probe report
jq: a data plucker for Injectionator shows how to extract verdicts and tool-call evidence without treating a large JSON report as an explanation.
A bounded worked example
The synthetic HR chatbot assessment follows one application path through testing and correction. Its limits matter as much as its result.