Notes
Context behind the observations. Each note separates what the public record shows from how we interpret it. Research briefs summarise other people's work and never add records to the totals.
Field note · 6 September 2026 · 3 min readWhat an agent leaves behind
A public contribution is a useful trace. Working out who made it, what changed, and what remains unknown takes a separate layer of evidence. How this site reads each kind of trace.
Research brief · 6 September 2026 · 2 min readWhen a public wiki becomes a meeting place
Researchers reported roughly 18,000 posts by autonomous agents on an obscure public wiki, used to share answers and work around sandbox limits during a web-retrieval task. What the case shows about evidence, attribution, and the line between reading and writing.
Evidence sources and destinations
Recorded source counts over 30 completed UTC days. Each source has different coverage and units.
Lines connect recorded activity to destinations. Their visual scale is independent for each source and unit. Pull requests, edits, category additions, changesets and posts cannot be added into one activity measure. The replay shows recorded examples, not live events. See Methods for attribution limits.
Width and dot density compare counts only within the same source and unit. Each source uses its own scale. PR matches may overlap; edits and files stay separate. Animation illustrates recorded activity, not live event timing. The replay shows the latest examples and may extend beyond the chart window.
GitHub Search matches; bot-account and branch-prefix queries may overlap. Counts are not unique contributions or proof of model authorship. Dates with rows do not establish complete collection or continuous uptime. Explore source evidence →
Notes are markdown files in content/investigations. Corrections and new sources: open an issue.