> 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.8-copyright-intellectual-property-and-protocol-stewardship.md).

# 13.8 Copyright, Intellectual Property & Protocol Stewardship

The public LPP ecosystem separates:

```
Research Disclosure
Licensing
Protocol Stewardship
Commercial Implementation
```

These are related.

They are not the same legal or governance function.

#### NateMind Ltd. Stewardship

The current public position is:

> **NateMind Ltd. is the steward of pre-existing LPP and Mind Universe research, protocol architecture, technical specifications, prototype work, and associated background intellectual property.**

This stewardship role includes maintaining the continuity of the LPP and Mind Universe technical architecture and public protocol record.

#### Artifact-Level Copyright

Copyright and authorship information should be read from the relevant artifact.

For example, published research papers identify their own author, publication record, and copyright or license information.

GitBook should not replace those artifact-specific notices with one universal statement.

#### Pre-Existing / Background IP

Public research and documentation may describe systems that are based on pre-existing:

* architecture,
* specifications,
* prototype work,
* governance models,
* and other background intellectual property.

Public disclosure of these materials does not itself transfer ownership of the underlying pre-existing rights.

#### Public Disclosure ≠ Ownership Transfer

The canonical public rule is:

```
Public Disclosure
≠
Transfer of Ownership
```

and:

```
Public Research
≠
Automatic Commercial Implementation Right
```

#### Artifact-Specific Licenses

A specific artifact may intentionally grant reuse rights.

Where it does, those rights are governed by that artifact's license.

This does not automatically alter the ownership or licensing status of other:

* technical specifications,
* private implementations,
* background architecture,
* or commercial integration assets.

#### Protocol Architecture Stewardship

The public protocol requires stable canonical definitions.

Protocol stewardship includes maintaining consistency across:

* protocol naming,
* canonical versions,
* terminology,
* official documentation,
* research records,
* and compatibility boundaries.

Public discussion, academic citation, or independent analysis does not transfer protocol stewardship.

#### Protocol Naming

Use of the name:

```
Lingua Pactum Protocol
LPP
Mind Universe
```

for accurate citation or descriptive reference should not be interpreted as transfer of:

* authorship,
* stewardship,
* endorsement,
* or commercial implementation rights.

GitBook v2.0 does not make a separate claim here regarding registered trademark status.

#### Public Research vs Proprietary Implementation

The architecture deliberately allows the public research layer and proprietary implementation layer to coexist.

Conceptually:

```
Public Research
        ↓
Defines and exposes concepts,
formal models,
and selected technical evidence
```

while:

```
Controlled / Proprietary Implementation
        ↓
May contain production hardening,
commercial adapters,
private deployment logic,
and protected engineering details
```

This separation is consistent with the P0–P3 disclosure model.