Trademark Policy

Permitted Uses

You may use the Aroha name and badge for the following purposes without prior written permission:

• ✅Refer to the Aroha Protocol by name in documentation, blog posts, and talks (e.g. "Built on Aroha Protocol")
• ✅Say your product "implements Aroha Protocol" or "is Aroha-compatible" if it genuinely does
• ✅Use "Aroha-conformant" with a tier qualifier (e.g. "Aroha-conformant Tier 2") after passing the conformance test suite
• ✅Fork the open-source code under MIT — you just cannot call your fork "Aroha"
• ✅Include the Aroha Protocol logo in a "built with" or "compatible with" section of your product page
• ✅Reference Aroha in academic papers, conference talks, or educational content

Prohibited Uses

The following uses are not permitted without explicit written permission from Aroha Labs:

• ❌Name your product, company, or service "Aroha" or any confusingly similar variant
• ❌Use the Aroha logo as your own product logo or favicon
• ❌Claim "Aroha-conformant" status without passing the published conformance test suite
• ❌Register domain names containing "aroha" in a way that implies affiliation with Aroha Labs
• ❌Use the Aroha name in paid advertising in a way that implies official endorsement
• ❌Resell the Aroha conformance certification or badge to third parties

Fork Policy

The Aroha Protocol source code is licensed under MIT License. You are free to fork, modify, and redistribute the code under the terms of that licence. When you fork:

• →Choose a new name for your fork — not "Aroha" or confusingly similar
• →You may state that your fork is "derived from" or "based on" Aroha Protocol
• →You must retain the MIT copyright notice
• →You cannot use the Aroha trademark, logo, or conformance badge
• →If your fork is protocol-compatible, consider contributing back via a PR instead

Protocol extensions (new message types, new capability schemas) that remain backward-compatible with Aroha 1.0 may apply for inclusion in the official specification via the RFC process — start the conversation on Discord in the #protocol-rfcs channel.

Conformance Certification Process

To use the "Aroha-conformant Tier N" designation officially:

1. 1

   Run the conformance test suite

   Use npx @aroha-sdk/conformance-tests --tier N --url https://your-agent.example.com and save the output JSON.

2. 2

   Submit a conformance claim

   Email conformance@aroha-labs.com with your agent DID, tier level, test output JSON, and production URL.

3. 3

   Wait for review

   The Aroha maintainer team will verify the test output and check the live agent within 5–10 business days.

4. 4

   Receive signed badge

   On approval, you receive a cryptographically signed badge token. Embed it in your X-Aroha-Conformance response header.

Contact