Citation

§1When to cite ATR

Please cite this specification — rather than only linking to a URL — in the following contexts. The cited version should be the latest version published on /spec at the time of writing, and the citation should include that version number (e.g. v3.0.0-alpha.1).

• Academic publications. Conference papers, journal articles, theses that reference the ATR rule format, an ATR engine, ATR benchmark results, or use ATR as a baseline for comparison.
• Security research and technical reports. External reports that reuse ATR rules, cite ATR coverage figures, or reference specific threats by their ATR-YYYY-NNNNN identifier in threat-intelligence documents.
• Institutional documentation. Standards-body publications, research-institute white papers, and government recommendations that list ATR as a reference standard or interoperability format.
• Sovereign-AI compliance and conformance filings. AI risk-management and agent-security filings submitted to regulators that cite ATR as the basis for the detection-rule layer, or declare an organization's ATR integration level by L1 / L2 / L3 conformance.

§2Citation Formats

Four common citation formats are provided below. Select the one required by your target journal or institution. BibTeX is native to LaTeX; APA is the social-sciences standard; IEEE is the engineering standard; Chicago is common in the humanities.

@misc{atr2026,
  title  = {ATR: Agent Threat Rules — Open Detection Standard for AI Agent Threats},
  author = {Lin, Kuan-Hsin and {ATR Community}},
  year   = {2026},
  version = {3.0.0-alpha.1},
  doi    = {10.5281/zenodo.19178002},
  url    = {https://agentthreatrule.org/spec},
  note   = {MIT license}
}

§3Related Identifiers

The following identifiers point to equivalent or derived distributions of this specification. The DOI serves as the long-term stable anchor for citation; the others are distribution forms.

The normative anchor for citation is the DOI. Zenodo holds an immutable snapshot per release; the GitHub repository tracks ongoing evolution; the npm and PyPI packages are distribution artifacts used by implementers.