Skip to content
Agent Threat Rules (ATR)中文
Governance

Governance is on the public record.

Who maintains ATR, how a rule gets in, how the spec changes, what conflicts the lead maintainer has: all of it is on this page, and all of it can be audited on GitHub. ATR is an MIT-licensed open standard, and no company owns it. A standard earns trust when anyone can audit its process. No authority has to vouch for it.

Current maintainers

Responsible for rule quality, PR review and releases.

Adam Lin
林冠辛
Lead Maintainer

Founder and main maintainer of ATR. Owns the RFC-001 quality bar, community outreach and the review of ecosystem integrations. GitHub: eeee2345 (Adamthereal).

[email protected]

Besides the lead maintainer, two more maintainers have write access on GitHub, and one collaborator triages issues. Merging pull requests still rests with the lead maintainer, and spreading that out comes next. The criteria for more maintainers are below. Evaluating a transfer to a neutral foundation, such as the Linux Foundation, OpenSSF or an equivalent, is on the roadmap. The goal is a Technical Steering Committee.

Merge policy

Six gates before any rule merges.

Gate 5 is a human review. Machines enforce the other five, and each leaves a trace in a public CI log. Anyone can see why a rule passed or why it was blocked. Quality does not rest on a maintainer's judgment alone. It also rests on tests anyone can re-run.

1 · Schema validation

A valid YAML schema, a valid regex with no ReDoS, and at least 1 TP and 1 TN.

2 · RFC-001 quality gate

A confidence score decides which detection lane a rule enters. It weighs precision, in-the-wild validation, coverage depth and documented evasions. A rule below the bar is never promoted to enforce, though it may still exist as advisory. The threshold is a published formula that anyone can recompute.

3 · Benign corpus 0 FP

A new rule must record zero false positives on the benign corpus gate that runs on every PR. That is the floor at merge time. After release, false-positive rates are to be measured lane by lane on a larger benign corpus, never as a single figure. The per-lane rates published earlier were withdrawn on 2026-09-19 and are pending re-measurement.

4 · Cross-rule conflict check

On the same input, a new rule must not conflict with existing rules.

5 · Human review

A maintainer reviews the regex shape, test-case coverage and source citation. The stable tier requires provenance that a human has reviewed.

6 · PR compliance

At most 10 new rules per PR. test_cases must include both true_positives and true_negatives.

Decision-making

Different changes have different bars.

Changing a rule and changing the spec are different acts. A wrong rule can be deprecated or revised. The spec is the contract every conforming engine relies on, so a change to it has to reach every implementer with time to react. The bar rises with the number of people a change affects.

Add a rule
1 maintainer approval + automated safety-gate pass

Rule PRs run through the six safety gates (see Merge policy above). Once they pass, one maintainer's review is enough to merge. A second reviewer is not required, because the gates already cover objective quality.

Spec amendment (SPEC.md)
RFC issue first + 14-day public comment window (30 days for complex proposals) + 2 maintainer approvals

The spec is the contract between all conforming engines. Any spec change starts as an RFC issue with a 14-day public comment window (30 days for complex proposals), so every implementer sees it. Only then is the PR accepted. In the current BDFL phase, the two approvals are the lead maintainer's and one other maintainer's. When the TSC is formed, the bar becomes a TSC majority.

Breaking change (SemVer major bump)
Spec-amendment process + 30-day advance notice + CHANGELOG entry

Any change that breaks the rule schema, the engine API or the meaning of an existing rule_id is breaking. Notice goes out 30 days ahead through GOVERNANCE.md, the CHANGELOG and an @adopters notification, so upstream adopters have time to react.

Add or remove a maintainer
All current maintainers approve + the invited person agrees in writing

Adding a maintainer needs every current maintainer's approval. Removal needs a 2/3 majority, which does not apply under BDFL.

Deprecate a rule
1 maintainer approval, with a 30-day grace period

A deprecated rule stays in the corpus, but engines MUST NOT enable it by default. After 30 days it may be removed from the corpus. Downstream adopters who depended on it can pin to a deprecated version.

Working group

There isn't one yet. The conditions for starting one are written below.

OASIS CTI, the OpenTelemetry SIGs and OWASP working groups all hold scheduled meetings. ATR is not yet big enough for standing meetings to be worth their cost. For now every discussion happens asynchronously and in the open, on the record in GitHub Issues and PRs. A standard with a handful of implementers should not set up a committee before anyone asks for one.

Whether one forms depends on demand. If you have integration work under way, want to push the spec in a particular direction, or represent an implementer that wants a structured voice in the process, open an issue whose title starts with [WG-proposal]. When three or more independent implementers ask for the same thing, the maintainers will schedule a recurring working-group meeting every two weeks. The trigger is written here, and anyone may invoke it.

Become a maintainer

Actively recruiting.

Merge rights resting with one person is the largest known structural risk to ATR. They spread out once contributors have merged enough pull requests to earn commit rights. More maintainers are being recruited.

Candidate criteria:

  • At least three substantive PRs merged in the ATR repo in the past six months (new rules, schema fixes, engine improvements, or substantive documentation rewrites)
  • Knows SPEC.md well enough to explain its conformance clauses
  • Can review asynchronously. There is no real-time requirement, but PRs should get a first review response within 7 days on average
  • Keeps a neutral tone when representing ATR in public (GitHub, issue comments, conferences), and does not imply any commercial interest

How to apply: write to [email protected] with the subject 'ATR maintainer application'. Include links to your recent PRs and the area you want to take on (rules / spec / engine / documentation).

Succession plan

If the lead maintainer becomes unavailable.

Short term (within 30 days): the CODEOWNERS file and CI keep running on GitHub, and pull requests can still be reviewed and merged. A new npm release, though, needs a maintainer with publish rights to approve it with 2FA; CI can only stage it. ATR does not depend on a single server or a closed system. The rules are plain-text YAML, and anyone can fork them.

Medium term: the other current maintainers take over PR review and merging. If that is not enough, interim maintainers will be sought among external contributors who have merged at least three substantive PRs in the past six months, have shown hands-on familiarity with the schema implementation, and can review asynchronously. No candidate is named before the invitation has been sent and accepted.

Long term: the ATR roadmap includes evaluating a transfer to a neutral foundation (Linux Foundation or OpenSSF). A transfer requires two or more external maintainers, and at least one organization willing to fund the overhead of governance.

Conflict-of-interest disclosure

Why this disclosure exists.

Interests: the maintainer founded and controls PANGUARD AI, INC., which sells AI agent security products built on ATR.

ATR (Agent Threat Rules) is an MIT-licensed open standard maintained under the Agent-Threat-Rule GitHub organization. The interest above is not hidden. Writing it down is part of the governance. The lead maintainer does have interests. So the decision process is open, and anyone can check whether those interests bent a decision.

The boundary: ATR's rules, CHANGELOG, benchmark data and documentation must not be distorted by any commercial interest. ATR's issue tracker and PR review are open to everyone, including competitors of that commercial interest. They may propose rules, review pull requests and fork the entire standard. GOVERNANCE.md is public on GitHub for anyone to audit.

If you see this boundary being crossed, open an issue on GitHub or email [email protected].

Contributor rights

All contributions are published under the MIT license. Contributors keep every right to use their attack research in any form. ATR carries the detection, not ownership of the research.

A contributor's name goes in the rule's author field.