> 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/14.-appendix/14.12-document-dependency-map.md).

# 14.12 Document Dependency Map

The frozen public dependency map is:

```
LPP × Mind Universe Constitution
        ↓
Protocol Core
        ↓
Research Papers
        ↓
Technical Specifications
        ↓
Admission Kernel MVP
        ↓
Public Documentation
```

This diagram represents documentation and technical dependency, not a claim that every later artifact has higher normative authority than every earlier artifact.

### Constitutional Layer

```
LPP × Mind Universe Constitution v1.1
```

Role:

```
Supreme normative principles
```

No runtime or research artifact may silently override it.

### Protocol Layer

Current existing core:

```
Protocol Core v1.1
```

Role:

> **Historical / transitional protocol core; current integrated public semantics are normalized by GitBook v2.0 pending Protocol Core v1.2.**

Target canonical revision:

```
Protocol Core v1.2 — Planned
```

It is not yet an existing published artifact.

### Research Layer

```
Paper 1 — Constitutional Admissibility
Paper 2 — Admission Kernel
Paper 3 — LPP-FIN
Paper 4 — Authority Objects
Paper 5 — Intent / Trajectory Governance
```

Role:

```
Formal research development
and published propositions
```

### Technical Specification Layer

Includes:

* CP / EP separation,
* Authority Layer security,
* Admission Artifact verification,
* interfaces,
* implementation-facing security requirements.

Role:

```
Engineering specification
```

### Implementation Layer

```
Admission Kernel MVP v0.1
```

Role:

```
Executable reference prototype
for selected protocol properties
```

### Public Documentation Layer

```
GitBook Public Documentation v2.0
```

Role:

```
Canonical public interpretation
and navigation across all layers
```

GitBook does not rewrite a paper's historical mathematics.

It defines how current readers should understand the combined architecture.