DIGGINGBEAGLE

Using the archive

Cite the claim you used

A case can change through a reviewed correction while its public URL stays stable. Cite the specific record and follow the source locator for factual claims.

Basic citation

Use DiggingBeagle as publisher, the exact page title, its canonical URL, and the publication date shown on the page. If no date is shown, record your own access date instead of assigning one to the article.

Example from this public library

DiggingBeagle. “What changes when one operator can run a multi-agent attack loop.” https://diggingbeagle.com/articles/what-changes-when-one-operator-runs-a-multi-agent-attack-loop/

Claim and source

For a specific factual assertion, link to the relevant claim within the case. Follow that claim's source link and preserve its locator when you cite the original material. A source can support a narrow assertion while leaving another point unresolved.

Updates

Check the current record and its linked updates and corrections before quoting an older summary. A changed title or conclusion should not be silently projected back onto the earlier version. The visible date refers to the record's stated publication or event field, never to a routine site rebuild.

Why this archive exists

The source matters after the headline fades.

DiggingBeagle is a non profit research project documenting AI security incidents, agent failures, vulnerabilities and AI-assisted operations. A case keeps its claims beside the sources that support, contest or limit them. Later updates stay visible, so a reader can see when the account changed.

We publish case reconstructions, dated reporting and analysis across records. Each has a different evidentiary role. About the project and our methodology explain how the work is reviewed.