Trademark Policy

Last updated: 30 July 2026

1. About this policy

1.1XORCISE.AI operated by Fifth Domain Pty Ltd ACN 606 251 585 ("XORCISE.AI", "we", "us" or "our") owns the XORCISE and XORCISE.AI names, the associated logos and wordmarks, and the `xorcise.ai` domain (together, the Marks).

1.2The software, the mission library, the playbooks skill and the documentation are licensed under the Apache License 2.0. That licence covers copyright and patents. It does not grant any right to use the Marks. Apache-2.0 section 6 says so expressly, and this policy sets out what we permit in addition.

1.3The reason we hold the Marks is narrow and it is the same reason the rest of the project is open: a result that carries the XORCISE name should have been produced by the engine and the rubrics published here. Trademark is the only mechanism that keeps "graded by XORCISE" meaning one thing.

2. What you may do without asking

2.1State truthfully that your software, service or result works with, is built on, is compatible with, or was produced by XORCISE. For example, "evaluated with XORCISE", "XORCISE-compatible harness", "a XORCISE run report".

2.2Use the word XORCISE in the ordinary descriptive sense in articles, talks, papers, blog posts, course material, benchmarks and comparisons, including critical ones.

2.3Redistribute the unmodified software, mission library or documentation under Apache-2.0, with the Marks intact as they were shipped.

2.4Use the logo unmodified to link to this site or to the repository.

2.5Publish results you produced with XORCISE, including results that make us look bad. We ask only that you state the conditions the run was carried out under, because a score without its conditions is not a result.

3. What requires our written permission

3.1Using the Marks, or a name or logo confusingly similar to them, as the name of your own product, service, company, application, domain or social account.

3.2Distributing a modified build of the software, or a modified mission library, under the XORCISE name. Fork freely; Apache-2.0 gives you that right and we are not going to interfere with it. But a fork that changes the engine, the graders or the rubrics must be named distinctly, so that a reader can tell whose grading produced a given number. Renaming a fork is not a barrier we put in the way of forking; it is the point of the fork being auditable.

3.3Presenting a score, leaderboard, certification, badge or seal as coming from XORCISE when it was not produced by the published engine against the published rubrics.

3.4Merchandise, event names, or any use that implies sponsorship, endorsement, partnership or affiliation that does not exist.

4. How we will apply it

4.1We will not use trademark law to suppress forks, criticism, comparative benchmarking, security research, or publication of unfavourable results. If you think we have, say so at the address below and we will answer publicly.

4.2Where we believe a use is outside this policy, our first step will be an email asking you to change it, with a reasonable period to do so.

4.3This policy may change. Changes are published here with a new date, and will not be applied retrospectively to a use that was permitted when you started it.

5. Requests and questions

5.1Requests for permission under section 3, and any question about whether a use is permitted, go to legal@xorcise.ai. Describe the use and we will give you a plain yes or no.