# ACES notices and records

**Legal framework version 1.0. Effective 5 November 2026.**

This register records adoption, contributor acceptance and notices for the ACES Working Group. Its exact filename is required by references in CSL. A record is not a patent-clearance opinion, a trademark registration or a substitute for the legal requirements of the full license.

## 1. Framework adoption and maintainers

**Record ACES-LF-2026-11-05: adopted and effective.**

| Item | Record |
| --- | --- |
| Effective date | 5 November 2026 |
| Adoption basis | Confirmation and publication instruction of Reuven Farchi, ACES Consortium coordinator |
| Adopted framework | ACES legal framework version 1.0: LICENSE.md (CSL 1.0), LICENSING.md, MEMBERSHIP.md, CONTRIBUTOR-AGREEMENT.md, CONTRIBUTING.md, Scope.md, Governance.md, TRADEMARKS.md and the notice/release procedures |
| Initial specification edition | ACES document revision 0.2.1, technical baseline 0.2 |
| Scope | Version 1.0, effective 5 November 2026 |
| Initial coordinator and maintainer | Reuven Farchi |
| Coordination contact | info@aces-consortium.org |
| File-set identification | The accompanying SHA256SUMS.txt identifies the supplied release files |

The coordinator confirms that the existing consortium members have been informed of these conditions and accept them as part of membership. Their acceptance is recorded on that basis; this record does not purport to reproduce individual signatures. Future membership acceptance is recorded through the process in `MEMBERSHIP.md`.

The framework is operative. No additional adoption vote or duplicate contributor signature is required by this framework before publishing the initial material identified below. Deployment and recording its actual public timestamp remain publication operations, not conditions delaying framework adoption.

## 2. Initial contributor and existing-material authorization

**Record ACES-CONTRIBUTOR-001: accepted.**

| Item | Record |
| --- | --- |
| Contributor | Reuven Farchi |
| Capacity | Initial technical contributor and consortium coordinator |
| Acceptance date | 5 November 2026 |
| Material covered | His original technical contributions comprising ACES baseline version 0.2 dated 21 September 2026 and their incorporation into document revision 0.2.1 |
| Specification terms accepted | Community Specification License 1.0, ACES contributor agreement version 1.0 and Scope version 1.0 |
| Code designation accepted | Apache License 2.0 for the JSON examples in Sections 5.4 and 5.5 and the preliminary JSON Schema in Annex A |
| Publication authorization | Publication of the identified contributions and effective legal framework on the ACES website and in the repository |
| Record basis | Direct written confirmation by Reuven Farchi on 5 November 2026 that he is the sole technical contributor to date, accepts the terms and directs publication-ready adoption |

The baseline source is `ACES Spec V0.docx`, version 0.2, with SHA-256 `766708d2e9f17fc7858d94903b87916581b471fa5c59109ebfc4fc6c1dd6a2c8`. Technical wording is preserved in revision 0.2.1 outside the licensing section and administrative front matter.

The authorization applies to rights the Contributor holds or is entitled to license, with the authority representations in CSL Section 8.1. Referenced external standards and unrelated third-party materials are not relicensed. No other member is recorded as having contributed technical material to this baseline. Membership alone does not assign authorship or ownership.

The acceptance date is not backdated to the baseline document date and is not a claim that a CSL exclusion period has already expired. Applicable periods and commitments are governed by the actual contribution history and CSL.

## 3. Subsequent membership and contributor records

For new members, record the member's legal identity, authorized representative, acceptance date, accepted document/Scope versions and a reference to the enrollment evidence. Existing members covered by the coordinator's confirmation in Section 1 do not need to re-sign merely to be entered individually in the register.

For a technical submission, identify the Contributor, represented entity if any, submission reference, material covered, date included in the draft and the applicable membership or non-member acceptance record. Obtain sufficient authority for third-party material and preserve notices. Keep confidential authorization documents and unnecessary personal data out of the public register.

Later withdrawals or changes do not erase historical records. Update this register with actual events, not assumed signatures or proposed acceptances.

## 4. Implementer acceptance under CSL Section 2.1.3.3

No separate repository-route implementer acceptance is recorded in this release. That does not describe implementers using the distribution-based routes in Sections 2.1.3.1 or 2.1.3.2.

To use the repository route, the implementer's authorized representative must issue a pull request or commit to this file containing an explicit acceptance of CSL, the implementer's legal name, the authorized individual's name and system identifier, and the exact ACES specification version. Also record the actual date, Scope/release reference and the original pull request or commit reference.

A suitable affirmation is:

> The identified implementer accepts Community Specification License 1.0 for the identified ACES version, including the applicable reciprocal patent terms. I am authorized to make this acceptance on that implementer's behalf.

Membership or contributor acceptance does not replace this distinct route. For a distribution route, include the full CSL as specified in the license, not only a link.

## 5. Patent exclusion notices

No patent exclusion notice is recorded as of the framework's effective date. This is a statement about this register, not a declaration that no patents or possible claims exist.

An Exclusion Notice must be issued by a pull request or commit to this file and satisfy CSL Sections 3 and 9.7. Identify the notifying party and representative, specification, relevant contribution or approval event, actual notice date and the patent information required by the license:

- For issued patents and published applications, include the patent numbers or application titles and numbers, as applicable.
- For unpublished applications, provide either the filed application text or the specific specification portions whose implementation makes the excluded claim a Necessary Claim, as allowed by Section 9.7. Do not require confidential application text when the license allows the latter route.

Retain the original notice and its timestamp, affected provisions, corrections and any separately recorded assessment or resolution. Section 3.1 provides the contribution-based 45-day rule and its limitation for material already in the draft. Section 3.2 separately addresses pre-approval exclusions; it does not reopen claims eligible under Section 3.1. The full license controls.

Issuing the required notice is distinct from maintainer approval of its substance. Preserve unmerged and disputed notices; do not conceal them by refusing a merge. Governance approval rules cannot cancel a valid exclusion. Resolve affected requirements under `Governance.md` before Approved Specification designation.

Where repository access is restricted, contact the coordinator promptly for a submission path. The coordinator must facilitate a timely repository action by the entitled party or its authorized agent. Email alerts and access requests do not by themselves replace the CSL repository requirement. Keep a public copy of current notices and versioned release snapshots.

## 6. Withdrawals

No Contributor withdrawal notice is recorded as of the framework's effective date.

A withdrawal under CSL Section 2.3 must be issued by pull request or commit to this file, identifying the Contributor, authorized representative and system identifier, actual date and original notice reference. Existing commitments remain in effect as stated in CSL; no new obligations are incurred after the effective withdrawal notice. A membership resignation and a CSL withdrawal are recorded separately when both apply.

## 7. Release designation and publication evidence

**ACES document revision 0.2.1** is designated an official **working-draft release** under legal framework 1.0 and Scope 1.0. It is not an Approved Specification. Its technical baseline remains version 0.2. The full file set is identified by `SHA256SUMS.txt`.

This record authorizes publication; it does not assert that deployment has already occurred or establish a first-publication timestamp. The maintainer records actual public URLs, first-publication date/time and evidence, exact source commit/tag and artifact hashes when deployment occurs. Preserve any independent archive/deposit reference and identify applicable open exclusion/review periods and later notices. A legal effective date or private commit alone is not public-disclosure evidence.

For a later Approved Specification, also record candidate review dates, contribution-period checks, notice resolutions, consensus evidence, decision authority, exact approved version and actual approval date. Keep earlier release snapshots unchanged.

## 8. Identity and certification records

The effective policy is `TRADEMARKS.md`. No trademark registration or product certification is asserted by this release. The coordination contact administers branding requests; any permission must be issued by the relevant rights holder or its authorized delegate.

Record actual trademark ownership, registrations, licensing delegations or certification authorizations when established. Do not infer a transfer of rights from framework adoption, membership or repository administration.