ĀML™ separates the rights granted for open-source software from rights associated with official branding, certification-style identity, managed infrastructure, commercial services, and future separately licensed products.
This page is intended to make that boundary easy to understand. It does not retroactively change rights already granted under the MIT License and is not a substitute for a signed commercial agreement.
Code distributed under the repository LICENSE remains available under the MIT License for the version in which it was distributed.
That license broadly permits use, copying, modification, distribution, sublicensing, and sale of the covered software, subject to the MIT notice and disclaimer.
A later change in repository structure or business model does not revoke MIT rights already granted for a copy that was validly distributed under MIT.
The MIT License does not itself grant permission to use ĀML™ or ĀRU™ trademarks, official logos, certification-style marks, endorsement language, official badge artwork, trade dress, or other source-identifying branding.
See TRADEMARKS.md for the current public brand-use policy.
Technical compatibility, interoperability, or use of MIT-licensed code does not by itself create:
- an official ĀML™ certification;
- an ĀRU Intelligence Inc.™ endorsement;
- a partnership or reseller relationship;
- an OEM/co-branding authorization;
- a right to use official compatibility badges;
- access to managed infrastructure, support, or private enterprise materials.
ĀRU Intelligence Inc. may offer commercial rights and services by written agreement, including:
- official ĀML Compatible™ or named conformance branding;
- official badge and trademark authorization;
- signed
aml-brand-authorization/1credentials; - enterprise architecture and implementation services;
- AI Interface Firewall™ integration services;
- OEM and embedded programs;
- “Powered by ĀML™” co-branding;
- managed policy, verification, trust, receipt, transparency, or revocation infrastructure;
- enterprise policy packs, deployment assistance, training, implementation review, and support;
- private or separately distributed commercial components where expressly identified under separate terms.
Nothing on this page grants those commercial rights automatically. They require an appropriate written agreement where applicable.
Future ĀRU products, hosted services, enterprise components, private modules, policy packs, datasets, signing services, or other materials may be distributed under commercial or other licenses instead of MIT.
A component is not made proprietary merely because it is described as “enterprise,” “official,” or “commercial.” Its applicable license must be stated with the component or in the controlling written agreement.
The MIT License continues to control software already released under MIT unless the relevant rights holder separately offers the same material under another license and the recipient accepts that alternative license.
No repository policy should be read as claiming ownership of third-party code, third-party trademarks, or contributor rights that have not been validly assigned or licensed.
Before incorporating outside contributions into a separately licensed commercial component, ĀRU should confirm that it has the rights necessary for that licensing model.
See CONTRIBUTING.md for the present contribution terms and the explicit no-silent-relicensing boundary.
ĀML™ was created by Daniel Jacob Read IV and is stewarded by ĀRU Intelligence Inc.™
Repository notices may identify the creator, copyright holder, project steward, package author, or trademark claimant in different capacities. Those labels should not be treated as proof of a legal assignment between persons or entities unless a separate signed instrument establishes one.
For commercial agreements, licensing should be executed by the person or entity that actually owns or is authorized to license the relevant rights.
See NOTICE.md for the concise public rights notice.
Nothing in the trademark policy, commercial materials, or first-use declarations should be interpreted as a patent filing, patent grant, or statement that any patent exists.
Potentially patentable inventions should be evaluated separately by qualified counsel, particularly before additional public disclosure.
The repository includes IP_PROTECTION_ROADMAP.md, which identifies the practical work that cannot be accomplished merely by adding GitHub notices, including chain-of-title documentation, trademark evaluation, copyright-registration review, patent timing, trade-secret boundaries, contributor-rights controls, and written commercial agreements.
That roadmap is an operational checklist, not legal advice.
For official branding, OEM/co-branding, enterprise integration, managed infrastructure, support, strategic partnerships, or separately licensed offerings:
For public, non-confidential first contact, use:
.github/ISSUE_TEMPLATE/commercial-license.md
Do not post confidential pricing, private keys, customer data, trade secrets, or confidential deal terms in a public GitHub issue.
LICENSE— license governing MIT-covered softwareLICENSING.md— canonical licensing architectureNOTICE.md— concise public rights noticeIP_PROTECTION_ROADMAP.md— operational IP-protection checklistTRADEMARKS.md— trademark and brand-use policyCOMMERCIAL.md— commercial relationship and services frameworkCONTRIBUTING.md— contribution and contributor-rights boundaryOFFICIAL_MARKS.json— machine-readable official-mark registryOFFICIAL_AUTHORIZATIONS.json— public authorization indexrfcs/0011-official-brand-authorization.md— signed authorization formatAML_SOVEREIGN_MARK_OFFICIAL_FIRST_USE.md— public first-use publication
This repository documents the project’s intended licensing and brand architecture. It is not legal advice, does not itself create a transfer of intellectual property, and does not replace trademark registrations, copyright assignments, patent filings, NDAs, commercial licenses, or other signed legal instruments where those are appropriate.