Skip to content

COMMERCIAL.md

Latest commit

 

History

History
145 lines (95 loc) · 5.83 KB

COMMERCIAL.md

File metadata and controls

145 lines (95 loc) · 5.83 KB
Raw

Commercial Licensing, Official Branding & Partnerships

ĀML™ is designed to spread broadly as open technology while preserving a controlled official brand, compatibility identity, enterprise ecosystem, and commercial relationship layer.

For the canonical licensing boundary, see LICENSING.md. For the operational IP-protection checklist, see IP_PROTECTION_ROADMAP.md.

Open-source software stays open

The software covered by LICENSE is available under the MIT License. You do not need to pay ĀRU Intelligence Inc.™ merely to exercise rights that the MIT License already grants.

That open-software position is intentional: adoption and interoperability should be easy.

The official layer is separate

Organizations should contact ĀRU when they want rights or services beyond the open software license, including official branding, formal commercial relationships, managed infrastructure, or direct support.

Official AML compatibility branding

Potential arrangements include:

  • official ĀML Compatible™ branding;
  • official named conformance-level branding;
  • authorized badge artwork;
  • verification against the official conformance suite;
  • signed aml-brand-authorization/1 credentials recording the authorized scope;
  • public listing of an authorization when both parties agree to publication.

Technical conformance can be independently tested without buying a brand license. Official branded status is a separate matter.

Enterprise implementation

ĀRU may provide or arrange commercial services such as:

  • AML architecture and adoption planning;
  • AI Interface Firewall™ integration;
  • policy architecture and policy-pack engineering;
  • accountable AI interface design;
  • enterprise conformance programs;
  • security and trust-fabric integration;
  • developer training;
  • implementation reviews;
  • private deployment assistance;
  • ongoing technical support.

OEM and embedded programs

Potential commercial arrangements include:

  • “Powered by ĀML™” programs;
  • embedded AML accountability inside another commercial platform;
  • OEM/co-branding;
  • white-label infrastructure where separately agreed;
  • product-specific official authorization;
  • marketplace, platform, or device integrations.

Managed infrastructure and verification

Future or negotiated services may include:

  • hosted verification endpoints;
  • managed policy registries;
  • signed authorization/credential issuance;
  • transparency/revocation infrastructure;
  • enterprise conformance reporting;
  • managed proof/receipt infrastructure.

Availability and commercial terms are determined by written agreement and should not be inferred merely from this roadmap.

Future separately licensed products

ĀRU may create future products, private modules, hosted services, enterprise policy packs, datasets, signing services, deployment tooling, or other components under separate commercial terms.

A future component is only outside the repository MIT grant when its applicable license or controlling written agreement actually says so. A marketing label such as “enterprise” or “commercial” does not itself change licensing.

Strategic partnerships

ĀRU is open to serious discussions with:

  • AI platform companies;
  • browser and runtime developers;
  • framework maintainers;
  • accessibility technology organizations;
  • security and identity companies;
  • universities and research groups;
  • standards participants;
  • enterprise software vendors;
  • regulated-industry technology providers;
  • agent/platform builders.

Signed official authorization

When useful, an official written authorization can be represented by a signed aml-brand-authorization/1 credential.

That credential can bind:

  • issuer;
  • grantee;
  • authorized marks;
  • permitted-use categories;
  • issue/expiration dates;
  • an agreement reference;
  • an Ed25519 public key/signature;
  • a revocable credential hash.

The credential is machine-verifiable evidence of the represented authorization scope. It is not a substitute for the written agreement that creates the legal relationship.

See:

  • rfcs/0011-official-brand-authorization.md
  • schema/brand-authorization.schema.json
  • OFFICIAL_MARKS.json
  • OFFICIAL_AUTHORIZATIONS.json

Why the distinction exists

ĀML intentionally separates:

  1. software freedom and interoperability, which accelerate adoption; from
  2. official brand authority, official compatibility identity, endorsement, commercial services, managed infrastructure, and future separately licensed offerings, which remain controlled when the relevant rights and agreements support that control.

A company can implement the open protocol without buying a license to the MIT-covered code. A company that wants to present itself as officially authorized, officially compatible, partnered, co-branded, or endorsed under reserved AML/ĀRU branding should contact the rights holder.

Start a commercial conversation

For official branding, enterprise, OEM, managed infrastructure, compatibility-brand authorization, or strategic partnership discussions:

Office@aruintelligence.com

Official website:

https://aruintelligence.com/

For a public/non-confidential first contact, use:

.github/ISSUE_TEMPLATE/commercial-license.md

Do not place trade secrets, passwords, private keys, customer data, confidential pricing, or confidential deal terms in a public GitHub issue.

No implied commercial relationship

Contact, technical conformance, contribution, use of MIT-licensed code, or participation in the open-source project does not itself create a trademark license, official compatibility authorization, certification, endorsement, partnership, exclusivity right, or other commercial relationship.

Any such rights must be granted in an appropriate written agreement by an authorized rights holder.

See TRADEMARKS.md for the brand-use policy and NOTICE.md for the concise public rights notice.