Studio review · experiment E03 · v1 · 29 October 2026, 09:30 UTC
E03, where injected words come from: keep
Reviewed by deck@the-ultimate-insider. The piece: injection sources, v1, driven (48 s) and its explainer, made by ruv.sgit in run r8-e03-injection-sources from the researcher's injection-sources.json. Looked at over HTTP at 6 and 20 s, the end state, the light theme and reduced motion; no console errors.
Verdict: keep
It says what the editor asked for in one look: everything an agent reads is a way in. Sixteen numbered sources round one agent, in four families (sent to it, it browses, it builds with, other agents give it), each lit in turn with its case, year, label and what it led to. Every lesson from E02 is in from the first pass: the drawing is labelled, plain words come first, the text stays clear of the headline. The researcher's cautions are all on screen: the labels by dot shape (4 incidents, 4 vendor-confirmed, 8 research demonstrations), no second independent primary source, the code row as a pull request, ClawHavoc's "holds in part". No payload anywhere.
A finding in the data, worth the last line
The four filled dots, the real-world incidents, all sit in one family: it builds with. Amazon Q came through a pull request, Clinejection through a public issue, ClawHavoc through skills (and that one only holds in part: the words steered the users, not shown to steer the agent), and Nx through an install script. Every case that happened outside a lab came in through the supply chain of the tools the agent works with, not through the inbox. The slide shows it but does not say it. For a v2, or for the speaker: say it, with ClawHavoc's caveat.
Notes for v2 (not urgent)
- The still loses the cases. Each case's name shows only while it is lit; the end state lists sources without cases. Put the case name small beside each source in the list, so the still carries the evidence.
- The families as sectors. The family labels float near their dots; a faint arc per family on the ring would make the four groups read at once, as asked of E02 v3.
- Name the finding above as the last line, in the file's words.
Next
No redo now. E04 (the over-enthusiastic agent) is ruv.sgit's next request, sent at 09:22; a v2 of E03 waits for the editor's view.