# License

This repository carries two kinds of material and licenses them differently.

## Prose — CC BY 4.0

`spec/`, `README.md` and any translations: **Creative Commons Attribution 4.0
International** (`SPDX-License-Identifier: CC-BY-4.0`).
Canonical text: <https://creativecommons.org/licenses/by/4.0/legalcode>

You may read, copy, quote, translate and adapt these documents, including in
contracts and in commercial work, with attribution to *PI Lab — SEAL Protocol*
and a link to the release you used.

Translation is deliberately permitted. A licence that forbade derivatives
would protect the wording and lose the point: a client who cannot render the
protocol in the language of their own contract cannot cite it.

## Conformance suite and test vectors — Apache-2.0

`conformance/` and `testdata/`: **Apache License 2.0**
(`SPDX-License-Identifier: Apache-2.0`).
Canonical text: <https://www.apache.org/licenses/LICENSE-2.0>

These are machine-consumed artefacts — an implementation embeds them and is
tested against them — so they carry a code licence, including its patent
grant, rather than a document licence.

The exam-method templates published by the reference implementation are prose
and carry the prose terms above.

## Implementing this protocol

**Implementation is royalty-free.** PI Lab grants no exclusivity over the
mechanisms described here and asserts no patent against an implementation of
this specification. The argument this protocol makes — *you do not have to
trust the issuer* — requires that anyone be able to write the verifier. A
licence that made implementation conditional would refute the claim it is
supposed to support.

Publication is also defensive: what is written here is prior art from the date
of its release tag.

## Using the name

"SEAL", "SEAL Protocol", the assurance grades and the badges are used to say
that a specific thing was done. So the name is conditional where the licences
are not:

- You **may** say an implementation *implements SEAL 0.2* once it passes the
  published conformance suite for that release and publishes its item-to-test
  mapping, including any exemptions and the reason for each
  (see [`conformance/README.md`](conformance/README.md)).
- You **may not** present a modified or partial protocol as SEAL, or issue
  certificates or grade badges under the name from a ledger that is not
  operated under this specification.
- Naming the specification in order to cite, criticise or compare it is always
  permitted, and needs no licence.

This is a condition on the name, not on the text. Fork the documents freely;
call the fork something else.
