> 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/11.-public-proof-and-validation/11.-public-proof-and-validation.md).

# 11. Public Proof & Validation

LPP separates architectural definition from executable implementation, validation evidence, and independent reproduction.

This separation is deliberate.

A protocol may be formally specified before every decision path has been implemented.

An implementation may exist before every property has been validated.

A validation result may exist before an external party independently reproduces it.

The governing rule is therefore:

> **Specified ≠ Implemented ≠ Validated ≠ Independently Reproduced**

Public Proof exists to make these boundaries inspectable rather than implicit.

The current public validation architecture contains three related but distinct layers:

**Protocol / Research Definition**\
↓\
**Admission Kernel MVP Implementation**\
↓\
**Public Proof v2.0 — Controlled Technical Evidence**

Public Proof does not replace the protocol specification.

It exposes bounded technical evidence for claims that have reached an implementation or validation state.