> For the complete documentation index, see [llms.txt](https://docs.lpp-minduniverse.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lpp-minduniverse.org/lingua-pactum-protocol-lpp-documentation/13.-reference-and-governance/13.7-licensing.md).

# 13.7 Licensing

LPP uses an **artifact-specific licensing model**.

There is no single assumption that one license automatically governs:

* research papers,
* GitBook documentation,
* GitHub code,
* technical specifications,
* diagrams,
* datasets,
* validation material,
* protocol naming,
* or commercial implementations.

The canonical rule is:

> **Each artifact is governed by the license or agreement applicable to that artifact.**

#### Public Availability

Public availability means that an artifact can be accessed publicly under its applicable terms.

It does not automatically mean:

```
public domain
```

or:

```
unrestricted derivative implementation
```

or:

```
unrestricted commercial deployment.
```

#### Research Papers

Zenodo research papers are governed by the license attached to the corresponding Zenodo record or publication artifact.

The applicable license should be checked at the artifact level.

The license of one paper does not automatically govern another paper or a technical implementation.

#### Documentation

GitBook documentation is governed by the terms assigned to the documentation artifact.

The fact that technical information is visible in GitBook does not by itself grant rights beyond the applicable documentation terms.

#### Code

Public code repositories are governed by the repository's applicable code license and associated notices.

Documentation availability does not substitute for a code license.

#### Technical Specifications

A technical specification may be publicly inspectable while carrying different reuse or implementation terms from an academic paper.

#### Commercial Implementation

Commercial implementation rights are governed separately from research disclosure.

A public research paper, public schema, or public technical explanation does not automatically transfer:

* proprietary implementation rights,
* enterprise integration rights,
* or rights to protected background technology.

#### License Silence

Where an artifact does not state a particular license, GitBook v2.0 does not infer one.

The relevant artifact notice or formal agreement controls.

***

###