# ACES identity, compatibility and certification policy

**Policy version 1.0. Effective 5 November 2026.**

## 1. Identity and open implementation

The ACES name, ACES Consortium identity, project logo and authorized certification identifiers distinguish the project and its official activities. CSL Section 5 does not grant trademark rights. This policy governs project identity and misleading affiliation; it does not add restrictions to CSL's copyright or patent grants.

Requests concerning logos, branding and certification claims are administered through **info@aces-consortium.org**. Permission must come from the relevant rights holder or its authorized delegate. This policy does not itself register a mark, assign ownership or assert exclusive rights over every use of the acronym. Use of a registered-mark symbol requires an applicable registration.

## 2. Accurate references and compatibility statements

Truthful references to ACES, links to the standard, criticism, reporting of tests and lawful descriptive or nominative uses are permitted. No permission is required under this policy for attribution required by the specification license.

An appropriate self-declaration for a partial draft implementation is:

> Implements the stated features of ACES working draft 0.2.1. Compatibility is self-declared by the manufacturer; this product is not ACES-certified.

Identify the actual version, profiles, implemented features, limitations and responsible implementer. Do not claim full conformance without supporting evidence. The phrase "ACES compatible" may be used descriptively when accurate; it must not imply consortium testing, certification or endorsement that has not occurred.

## 3. Official releases and derivatives

Official releases are designated through `Governance.md` and `Notices.md`. A derivative, fork or independently hosted copy does not acquire that designation or ownership of other parties' material merely by using it.

CSL permits derivative specifications and does not require every fork to publish its additions under the same license. Unofficial derivatives must not be misleadingly presented as official ACES releases. Use a distinct title and a clear statement of unofficial status, while preserving the source attribution required by CSL. Historical quotation and accurate statements that a document is based on ACES remain permitted.

Independent implementation and commercial products are welcome. This policy does not prohibit legitimate competition or make consortium membership a prerequisite to truthful compatibility claims.

## 4. Logos, endorsement and certification labels

Do not use the ACES logo, a confusingly similar badge, or "ACES Certified" to claim product certification or endorsement without written authorization from the entitled rights holder or its delegate. Members must observe this rule as a membership condition; non-members remain subject to applicable rights and law.

Preserving a logo in an unmodified official document to identify its source is distinct from applying it as a product badge. Permission to reproduce the artwork itself depends on the accompanying rights. Lawful exceptions are unaffected.

## 5. Certification status and process

No operational product certification program is established by specification revision 0.2.1. This is the current certification status, not a limitation on the effectiveness of this policy. Membership, contributor acceptance, independent testing and implementation of a draft do not confer certification.

Before issuing certification, the consortium must publish the authorized operator and rights holder, eligible specification versions and profiles, tests and assessment procedure, permitted claims, any fees, validity and renewal, suspension and appeals. Record the scope of each actual authorization. Interoperability certification must not be represented as regulatory safety approval or patent clearance.

## 6. Concerns and corrections

Report suspected misleading claims to the coordination address with the exact statement, location and supporting evidence. Maintainers must review the actual rights and facts, preserve records and seek proportionate correction. Decisions affecting membership or project permissions are subject to the appeal process in `Governance.md`. This policy does not guarantee enforcement against every unauthorized use.