> 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.9-citation.md).

# 13.9 Citation

Different LPP artifacts should be cited according to what is actually being referenced.

The general rule is:

> **Cite the specific artifact that supports the claim.**

Do not cite a GitBook summary when a formal research paper is the actual source of a mathematical proposition.

Do not cite a research paper as evidence that an MVP behavior has been validated.

Do not cite a historical white paper as the current canonical definition when a newer canonical specification exists.

### Citing LPP as a Protocol

When referring to the current integrated protocol architecture generally, cite GitBook Public Documentation v2.0 together with the specific published research or technical specification that supports the claim.

Protocol Core v1.2 is a planned canonical revision and must not be cited as an existing publication until released.

Recommended pattern:

```
LPP × Mind Universe.
Public Documentation, v2.0.
NateMind Ltd., 2026.
```

Where a claim specifically concerns Protocol Core v1.1, cite v1.1 as a historical / transitional specification.

Where a future Protocol Core v1.2 is published, use that artifact's exact publication metadata.

### Citing GitBook

```
LPP × Mind Universe.
Public Documentation, v2.0.
NateMind Ltd., 2026.
https://docs.lpp-minduniverse.org/
```

For a specific page, include:

* chapter title,
* section title,
* documentation version,
* and access date where required.

### Citing Research Papers

#### Paper 1

```
Liao, Jason.
Lingua Pactum Protocol:
Constitutional Admissibility for AI-Triggered Language and Action.
v0.1. Zenodo, 2026.
DOI: 10.5281/zenodo.20373354
```

#### Paper 2

```
Liao, Jason.
LPP Admission Kernel:
Formal Operational Semantics for Layer 0
AI-Triggered Action Admissibility.
v0.2. Zenodo, 2026.
DOI: 10.5281/zenodo.20726851
```

#### Paper 3

```
Liao, Jason.
LPP-FIN:
Pre-Execution Admissibility for AI-Triggered Financial Actions.
v0.2.1. Zenodo, 2026.
DOI: 10.5281/zenodo.21253652
```

#### Paper 4

```
Liao, Jason.
Authority Objects for AI-Triggered Execution.
v0.2. Zenodo, 2026.
DOI: 10.5281/zenodo.21468687
```

#### Paper 5

```
Liao, Jason.
Latent Intent Mismatch and Semantic Verification:
Trajectory-Level Intent Admissibility for AI-Triggered Execution.
v0.3. Zenodo, 2026.
DOI: 10.5281/zenodo.21526037
```

### Version-Specific DOI Practice

When a claim depends on a specific published manuscript state, use the DOI associated with the relevant published version or record.

Do not assume that a future revision has identical formal content.

### Citing Technical Specifications

Technical specifications should include:

```
Specification Title
Version
NateMind Ltd.
Year
```

Example:

```
LPP Admission Kernel —
Control Plane Separation Model.
v1.0. NateMind Ltd., 2026.
```

or:

```
LPP Admission Kernel —
Admission Artifact Verification Specification.
v1.0. NateMind Ltd., 2026.
```

Where a specification provides a more explicit copyright, authorship, or publication notice, that notice should govern the formal citation.

### Citation Does Not Imply License

```
Can cite
```

does not automatically mean:

```
Can reproduce or commercially implement
without regard to the applicable license.
```

Likewise, licensing rights do not remove the scholarly requirement to attribute a source where attribution is required.