> 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.5-document-version-matrix.md).

# 13.5 Document Version Matrix

LPP × Mind Universe uses independent version lines for different artifact classes.

This prevents version numbers such as:

```
v0.4.1
v1.1
v0.2
v5.0 / planned v5.1
```

from being incorrectly interpreted as one global sequence.

### Independent Version Domains

#### Constitution

Uses its own constitutional version.

It changes through constitutional amendment.

#### Protocol Specification

Uses its own protocol-specification version.

#### Research Papers

Each paper has its own manuscript version and DOI record.

Paper versions do not replace the Protocol version.

#### Subsystem Specifications

Jarvis, ActuMind, SVNN, SourceMind, and other subsystems maintain independent versions.

#### Implementation

Admission Kernel MVP and later software implementations maintain implementation versions.

#### Documentation

Website and GitBook releases use separate documentation versions.

### Release-Status Rule

> **Planned canonical version numbers are not existing artifacts.**

A target revision must not be cited, linked, or presented as published until the corresponding document actually exists.

GitBook v2.0 may normalize the current canonical role of a subsystem before a new standalone subsystem specification is published.

Role normalization and document publication are separate status dimensions.

### Current Artifact / Target Revision Matrix

| Artifact Family                        | Existing / Current Status                                                          | Target Canonical Revision                                  |
| -------------------------------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| LPP × Mind Universe Constitution       | v1.1 — Canonical Normative                                                         | —                                                          |
| LPP Whitepaper                         | v0.4.1 — Historical / Foundational                                                 | —                                                          |
| GitBook Public Documentation           | v2.0 Release Candidate                                                             | Current RC; v2.0 canonical upon publication                |
| LPP Protocol Core                      | v1.1 — Existing; Historical / Transitional                                         | v1.2 — Planned Canonical Specification                     |
| Paper 1 — Constitutional Admissibility | v0.1 — Published                                                                   | —                                                          |
| Paper 2 — Admission Kernel             | v0.2 — Published                                                                   | —                                                          |
| LPP-FIN                                | v0.2.1 — Published                                                                 | —                                                          |
| Authority Objects                      | v0.2 — Published                                                                   | —                                                          |
| Paper 5 — Latent Intent Mismatch       | v0.3 — Published                                                                   | —                                                          |
| Admission Kernel MVP                   | v0.1 — Executable Prototype                                                        | —                                                          |
| Jarvis Governance Kernel               | v5.0 — Existing; pre-v2.0 role definitions                                         | v5.1 — Planned LPP-aligned revision                        |
| ActuMind                               | Legacy definitions embedded in existing documents; role normalized by GitBook v2.0 | v2.0 standalone specification — Planned                    |
| SVNN                                   | Paper 5 + legacy SVNN materials — Research / technical lineage                     | Standalone specification — Planned; version not yet frozen |
| Mind Universe Architecture             | Integration Map v1.2 — Existing legacy architecture                                | Architecture v2.0 — Planned                                |

### Protocol Core v1.0 / v1.1

Earlier Protocol Core versions remain part of the technical history.

```
Protocol Core Public v1.0
=
Legacy public specification
```

```
Protocol Core Integrated v1.1
=
Historical / transitional source
```

They contain important technical lineage but also include concepts that no longer match current v2.0 terminology.

The target protocol revision is therefore:

```
Protocol Core v1.2 — Planned
=
Planned Canonical Specification Line
```

Until v1.2 is actually published, Protocol Core v1.1 remains the existing historical / transitional core document, while GitBook v2.0 provides the current integrated public interpretation across later research and technical specifications.

Earlier versions remain citable as historical sources.

### Version Does Not Equal Evidence Status

A higher version number does not necessarily mean stronger implementation evidence.

For example:

```
Research Paper v0.3
```

and:

```
MVP v0.1
```

belong to different artifact classes.

Neither version number ranks the other.

This is why Chapter 11 separately tracks:

```
Specified
Implemented
Validated
Independently Reproduced
```