> 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.10-historical-documents.md).

# 13.10 Historical Documents

Historical documents remain part of the LPP × Mind Universe development record.

They should not be deleted simply because the architecture has matured.

However:

> **Historical documents do not override current canonical definitions.**

The historical corpus includes:

* LPP Whitepaper v0.4.1,
* previous GitBook editions,
* Protocol Core v1.0,
* Protocol Core v1.1,
* legacy ActuMind materials,
* legacy SVNN materials,
* DefendMind,
* previous Mind Universe architecture documents,
* and previous Jarvis terminology.

### LPP Whitepaper v0.4.1

**Status: Historical / Foundational**

The Whitepaper remains important for understanding the early development of ideas such as:

* language sovereignty,
* sentence responsibility,
* semantic governance,
* FaithLocked,
* SCSP,
* and early LPP architecture.

It is not the current canonical protocol definition.

### Previous GitBook

Previous GitBook editions are treated as:

> **Legacy Source Corpus**

They preserve the development path through concepts including:

* Sentence Sovereignty,
* SSB,
* SCoT,
* FaithLocked,
* SVNN,
* Jarvis,
* ActuMind,
* DefendMind,
* early Protocol Core,
* Admission Kernel,
* and Authority Objects.

The old GitBook remains historically valuable.

Its architecture should not be interpreted as the current canonical integration model.

### Protocol Core v1.0

Status:

> **Legacy Public Specification**

It established important early concepts including:

* constitutional admissibility,
* T0–T4,
* Authority lifecycle,
* cross-system recognition,
* SCSP safeguards,
* and the rule that LPP governs admissibility rather than execution.

### Protocol Core v1.1

Status:

> **Historical / Transitional Source**

It substantially expanded:

* Authority Object grammar,
* state transitions,
* cross-system transfer,
* collapse logic,
* T0–T4,
* SCSP Lock,
* and public schema work.

However, it also contains legacy architecture involving:

* conflicting SSB meanings,
* earlier SVNN consensus assumptions,
* old sovereign-recognition mechanisms,
* adaptive legitimacy constructs,
* and terminology not fully aligned with the current research chain.

It should not be silently edited and re-presented as the current specification.

### Legacy ActuMind

Earlier ActuMind materials used:

```
T0–T3
```

and positioned ActuMind as a final execution-authorization layer.

GitBook v2.0 replaces this with:

```
AM-R0–AM-R3
```

and:

> **Action Consequence & Execution-Readiness Governance Layer**

Legacy:

```
ActuMind PASS
→ final execution authorization
```

Current:

```
ActuMind PASS
→ may proceed toward LPP Admission
```

### Legacy SVNN

Earlier materials sometimes treated SVNN as:

* a semantic-consensus authority,
* a final legitimacy mechanism,
* a distributed governance source,
* or a system capable of producing authority-like consensus.

This is no longer canonical.

Current:

```
SVNN
=
Verification Evidence Substrate
```

and:

```
Admission Kernel
=
Constitutional Decision Layer
```

SVNN cannot manufacture missing authority.

### DefendMind

**Status: Historical / Applied Productization Lineage**

DefendMind was developed as a downstream applied governance system under LPP principles.

It is not part of the LPP protocol and does not define or extend constitutional authority.

DefendMind remains part of the historical productization lineage of the pre-action governance architecture.

It helped express the practical concept of a:

```
Pre-Action Governance Gate
```

for consequential domains.

DefendMind is not maintained as a parallel top-level canonical protocol layer in GitBook v2.0.

Its useful ideas have been absorbed into:

* Admission Kernel deployment,
* domain profiles,
* execution gating,
* and pre-execution governance concepts.

Current reading rule:

> **References to DefendMind should be read as historical productization of pre-action governance at the execution boundary, not as an independent authority source or a competing Admission Kernel.**

### Previous Mind Universe Architecture

Earlier Mind Universe documents contained a broader set of:

* semantic-governance systems,
* family and organizational subsystems,
* application modules,
* sentence-governance flows,
* and earlier relationships between Jarvis, ActuMind, SourceMind, SVNN, and LPP.

The current canonical relationship is:

```
LPP
=
Constitutional Protocol
```

```
Mind Universe
=
Governance Architecture
```

and:

```
LPP
≠
Mind Universe
```

### Previous Jarvis Terminology

Earlier Jarvis specifications use:

```
Admission Kernel
```

for statement-level semantic intake.

GitBook v2.0 resolves this as:

```
Legacy:
Jarvis Admission Kernel

Canonical:
Semantic Admission Layer
```

The name:

```
LPP Admission Kernel
```

is reserved for Layer 0 action admissibility.

### Historical Terminology Boundary

Key changes:

```
Jarvis Admission Kernel
→ Semantic Admission Layer
```

```
ActuMind T0–T3
→ AM-R0–AM-R3
```

```
Sovereign Signature Badge / SSB
→ Deprecated
```

```
Sovereignty Seal Badge / SSB
→ Deprecated
```

If SSB is retained in historical language-governance context:

```
SSB
=
Sovereign Sentence Badge only
```

```
ActuMind final authorization
→ Deprecated
```

```
SVNN as authority source
→ Deprecated
```