open-standards/wai/TRADEMARKS.md
Transaction Science bd54502a5e
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 8s
WAI breaking changes and the conformance runner / WAI breaking · does this change touch WAI (pull_request) Successful in 8s
WAI conformance / does this change touch it (pull_request) Successful in 8s
WAI energy receipts / does this change touch it (pull_request) Successful in 7s
WAI conformance / fast integer kernels, every x86_64 kernel set (AVX-512 silicon) (pull_request) Successful in 3m18s
WAI breaking changes and the conformance runner / WAI breaking · wire, record and API against main · linux (pull_request) Successful in 34s
WAI conformance / faces from keypoints under wasm32-wasip2 (wasmtime) (pull_request) Successful in 1m34s
WAI conformance / cross-arch byte-equality · linux (pull_request) Successful in 1m16s
WAI breaking changes and the conformance runner / WAI breaking and conform · their tests, and the independent verifiers through wai conform · linux (pull_request) Successful in 3m3s
WAI conformance / quantum core and corpus under wasm32-wasip2 (wasmtime) (pull_request) Successful in 3m44s
WAI conformance / cargo-class corpora · linux (pull_request) Successful in 17m18s
WAI energy receipts / energy receipts · linux (pull_request) Successful in 18m25s
WAI conformance / cross-arch byte-equality · macos (pull_request) Successful in 1m12s
WAI conformance / codec wrappers · fuzz smoke, text decode limits, C entry points, provenance, the semantic path (pull_request) Successful in 1m45s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 11m49s
WAI conformance / cargo-class corpora · macos (pull_request) Successful in 15m6s
WAI energy receipts / energy receipts · macos (pull_request) Successful in 23m59s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 2m45s
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Successful in 23s
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 6m38s
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 18s
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 37s
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 1m56s
WAI conformance / each feature of the independent verifiers' steps compiles alone (pull_request) Successful in 14m56s
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 14m8s
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Successful in 25m1s
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 1h24m50s
wai: the marks: .WAI™, WA²ISM™ and WAISM™, what anyone may do without asking, and what needs permission
The README's and the specification's titles carry .WAI™. Bare WAI and every
identifier stay as they are. CHARTER.md now says what Appendix C and
wai/LICENSE already say about WAI's specification text.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-05 11:02:17 -05:00

1.1 KiB

The marks

.WAI™, WA²ISM™ and WAISM™ are trademarks of Transaction Science, Inc.

  • .WAI™ is the name of the format and its toolchain, from Transaction Science.
  • WA²ISM™, also written WAISM™, is the name of the deterministic WebAssembly module profile.

What you may do without asking

The Apache License 2.0 covers the specification and the code. Section 6 of that licence does not grant the marks. Anyone may, without asking:

  • use the plain name WAI, the .wai file extension and every identifier the specification defines, in code, files, documentation and conversation;
  • say accurately that a product reads or writes .wai files, implements the specification, or passes wai conform;
  • fork and change the specification and the code, as the licence allows.

What needs permission

  • Naming a product, service, company or domain with one of the marks.
  • Calling a changed specification or a fork by one of the marks.
  • Implying that Transaction Science made, certified or endorses something it did not.

Write to [email protected].