Errata
Errata
A standing record of errors found in published versions of the ATR specification — kept in the open the way W3C and IETF specifications carry their errata. Every published version is permanent; the errors in it are corrected here, in public, with attribution. Each entry names the affected version, where the error sits, the corrective text, and the date the correction was published.
Errata Registry
No errata are on record for the current Working Draft. The absence of entries is not a claim of perfection — it means no error has yet been confirmed in a published version. If you find one, open an issue on the repository; a confirmed report is added here, not quietly patched.
How to report an erratum
Reporting an erratum is part of open review, and anyone may do it. If you discover an error in this specification, open an issue on the ATR repository. The report should include: the affected version, the section (e.g. §3.5), the erroneous text as published, the proposed correction, and any verifiable references. Maintainers review reports in reasonable time; once confirmed, the entry is added to the registry above, with attribution. Errors are not silently overwritten — they leave a record.
- Open an issue ↗ — github.com/Agent-Threat-Rule/agent-threat-rules/issues/new
- Editor contact: [email protected]
An erratum corrects the text, not the normative content — it is not treated as a spec change. Substantive semantic changes ship as new versions, tagged on /changelog as [Breaking] or [Compatible]. The line is deliberate: anyone citing this specification can rely on errata never shifting a rule's meaning underneath them.