The MIT license covers the code. It does not cover the names. This page describes appropriate and inappropriate use of our names and brand.

Saying you use our tools

Factual statements are always fine, in docs, marketing, receipts, or anywhere else:

• “Built on LemmaScript”
• “Verification powered by LemmaScript”
• “Uses claimcheck to natural language specs against Dafny proofs”
• Naming the pinned tool version and commit your product runs

Linking to our docs, case studies, and repositories is welcome. So is publishing benchmarks or evaluations of LemmaScript, favorable or not.

What to avoid

Please don't use our names in your product name, company name, domain, package name, or structural identifiers like schema namespaces. Identifiers travel without context, and a name in a namespace reads as a co-branded system. A data field naming the tool and version is a more accurate representation. Additionally, please don't state or imply that Midspiral reviewed, certified, or endorsed your product unless we've agreed to that in writing.

Working with us

We're happy to selectively collaborate on open-source and research projects as time and focus allow. Do reach out with open source projects or research ideas if you feel it's a good fit.

For commercial products integrating LemmaScript or other Midspiral tools, hands-on support (e.g., integration review, feedback, analyses, feature requests and other ongoing support) happens through paid engagements. If that would be useful, get in touch: hello@midspiral.com.

Certification or endorsement of a product built on our tools is only available through a formal agreement.