> 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.15-migration-notes-gitbook-v1.x-v2.0.md).

# 14.15 Migration Notes — GitBook v1.x → v2.0

GitBook v2.0 is not a cosmetic update.

It represents a structural normalization of the public LPP × Mind Universe architecture.

### A. Terminology Changes

#### LPP Positioning

Earlier public language frequently emphasized:

```
Language Sovereignty
Sentence Governance
Semantic Governance
```

Those concepts remain part of the historical foundation.

The canonical technical positioning is now:

> **LPP = Layer 0 Constitutional Admissibility Protocol for AI-triggered execution.**

The change does not erase language governance.

It places the current protocol boundary at the point where AI-generated language becomes consequential action.

#### Jarvis Admission Kernel

Legacy:

```
Jarvis Admission Kernel
```

Current:

```
Semantic Admission Layer
```

Reason:

```
LPP Admission Kernel
=
Layer 0 Constitutional Admissibility Kernel
```

#### ActuMind

Legacy:

```
Execution Governance Layer
final authorization
T0–T3
```

Current:

```
Action Consequence &
Execution-Readiness Governance Layer
AM-R0–AM-R3
```

ActuMind can restrict or escalate.

It does not grant final Layer 0 legitimacy.

#### SVNN

Legacy interpretations sometimes positioned SVNN as:

* authority-like consensus,
* sovereign recognition mechanism,
* or final consensus decision layer.

Current:

```
SVNN
=
Semantic Verification Node Network
=
Verification Evidence Substrate
```

Canonical rule:

> **SVNN provides evidence. Admission Kernel decides admissibility.**

### B. Architecture Changes

#### Old Public Model

The v1.x public edition was intentionally highly abstract.

Its Appendix explicitly avoided:

* operational flows,
* schemas,
* hashing methods,
* routing sequences,
* detection logic,
* and technical implementation detail.

#### New Public Model

v2.0 introduces:

```
Authority
→ Intent
→ Semantic / Task Governance
→ Action Candidate
→ Semantic Verification
→ Admission
→ Permit
→ Execution
→ Evidence
```

The new public architecture explicitly separates:

* Authority Plane,
* Semantic & Task Governance Plane,
* Verification Plane,
* Admission Plane,
* Control Plane,
* Execution Plane,
* Evidence Plane.

### C. Deprecated Concepts

No longer part of the canonical main path:

```
Sovereign Signature Badge / SSB
Sovereignty Seal Badge / SSB
ActuMind as final admission authority
SVNN as authority source
Jarvis statement Admission Kernel under that same name
legacy assumption that Mind Universe and LPP are one layer
```

These remain available in historical documents where necessary for provenance.

### D. Research Additions

v2.0 integrates:

```
Paper 1 — Constitutional Admissibility
Paper 2 — Admission Kernel
Paper 3 — LPP-FIN
Paper 4 — Authority Objects
Paper 5 — Latent Intent Mismatch & Semantic Verification
```

This adds or formalizes:

* Layer 0 / Layer 1 separation,
* Authority Objects,
* Execution Permit,
* Admission Artifact,
* T0–T4 ownership,
* Human-Authorized Intent,
* Authority–Intent Binding,
* Material Mutation,
* Re-Admission,
* trajectory-level governance,
* risk-indexed SVNN verification.

### E. Validation Changes

v2.0 formally distinguishes:

```
Specified
Implemented
Validated
Independently Reproduced
```

Current state:

```
ADMIT
=
Implemented + Validated

DENY
=
Implemented + Validated

DEFER
=
Specified

COLLAPSE
=
Specified
```

The current six execution-scenario set and separate Artifact Verification / Audit Reconstruction track are now part of the canonical public documentation.

### F. Disclosure Changes

v2.0 introduces:

```
P0 — Public Normative
P1 — Public Technical
P2 — Controlled Technical
P3 — Confidential / Secret
```

This changes the public strategy from:

```
Public
=
mostly conceptual abstraction
```

to:

```
Public
=
enough normative + technical material
for serious inspection,
research,
interoperability,
and eventual reproduction
```

without requiring disclosure of:

* production secrets,
* private keys,
* confidential deployment details,
* or commercially sensitive implementation logic.

### Migration Summary

```
GitBook v1.x
Conceptual Governance Description
        ↓
GitBook v2.0
Canonical Technical Documentation
```

```
Broad Language Governance
        ↓
Layer 0 Constitutional Admissibility
```

```
Overlapping Module Roles
        ↓
Explicit Authority Boundaries
```

```
Single Public-Abstraction Boundary
        ↓
P0 / P1 / P2 / P3 Disclosure Model
```

```
Conceptual Proof
        ↓
Specified / Implemented /
Validated / Reproduced
Evidence Discipline
```

This is a consolidation of the architecture, not a deletion of its history.