Conformance
Conformance
A rule written in Taipei should run unchanged on an engine in Seattle. Conformance is what makes that true. Three levels spell out what a system has to do before it can say it implements ATR. The test fixtures are in the repository, and no engine claims conformance yet.
L1 engine conformance Normative
The L1 engine is what makes the format portable. It MUST parse every rule that validates against spec/atr-schema.yaml. It MUST evaluate detection.conditions with the semantics in §3.5, and it MUST honor the scan_target and status semantics. That way a rule gets the same verdict no matter who wrote the engine. An L1 engine MAY refuse rules outside the scan_target it declares.
L2 publisher conformance Normative
An L2 publisher puts out rules in its own vendor-prefixed range, such as ACME-YYYY-NNNNN, and follows every ATR semantic. It MUST honor the deprecation policy in §3.7 and SHOULD include test_cases with every rule it publishes.
L3 sub-range authority Normative
An L3 sub-range authority is a national or organizational body that issues rules under a sovereign prefix, such as ATR-TW-2026-NNNNN. Authority is granted through the procedure in /charter §5. Once the TSC is seated, it grants it. Until then the lead maintainer (BDFL) does.
The TSC is not yet seated. L3 authority is granted once it is, and the TSC then also does the self-certification check in §5. Until then the lead maintainer (BDFL) does both.
Test suite
Conformance material lives in two places, and they are not reconciled yet. The suite you can run today is conformance/v1.0/. It has true-positive and true-negative fixtures for 103 rules, plus 20 edge cases. There are 836 rules, so the rest have no fixture yet. The suite does not yet pass end to end on the reference engine. Its README lists each fixture that fails.
conformance/v1.0/
├── fixtures/
│ ├── tp/<rule_id>/input.yaml + expect.json
│ ├── tn/<rule_id>/input.yaml + expect.json
│ └── edge/<case_id>/input.yaml + expect.json
├── runner/run-conformance.ts
├── README.md
└── SUITE.md
spec/conformance/ (not ratified)
├── baseline/
├── README.md
└── SIGNING.mdspec/conformance/ is a proposed corpus. Its README marks it as not ratified and says no engine claims ATR conformance. It holds 1 fixture so far. The conformance/v1.0 README defines L1 to L3 by test results, which is not the same as the three levels on this page.
Self-certification
To self-certify, run the test suite locally, then open a pull request against ADOPTERS.md with your integration details. The maintainers can check any self-certification at any time by re-running the suite against a published artifact. Once the TSC is seated, it takes that on.
Who does this check: see §3.
After passing the test suite, implementers open a pull request against ADOPTERS.md. The entry gives the organization name, the spec version, the integration date (ISO 8601), a public evidence link anyone can verify, and the conformance level they claim. Maintainers aim to validate and merge within seven days. The full procedure and the list of merged implementers are at /implementers.
