> 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.2-evidence-states.md).

# 11.2 Evidence States

The four evidence states have distinct meanings.

### Specified

Specified means that a behavior, object, property, rule, decision state, or interface is defined in an identified normative or research source.

Examples include:

* Layer 0 Constitutional Admissibility,
* Authority Objects,
* Human-Authorized Intent,
* ADMIT / DENY / DEFER / COLLAPSE,
* T0–T4,
* Material Mutation,
* Semantic Verification,
* Control Plane / Execution Plane separation,
* Execution Permits,
* and Admission Artifact verification.

Specified means:

> The behavior or structure has been defined.

It does not necessarily mean:

> Executable code exists.

***

### Implemented

Implemented means that the relevant behavior exists in executable code or prototype behavior.

The current Admission Kernel MVP implements a bounded subset of LPP.

Implementation evidence includes mechanisms such as:

* Control Plane behavior,
* Execution Plane Gate Hook behavior,
* signed Permit handling,
* Authority Record state,
* scope enforcement,
* expiration handling,
* nonce consumption,
* revocation handling,
* execution-intent binding,
* policy binding,
* and Admission Artifact generation.

Implemented means:

> The defined behavior exists in an executable system.

It does not automatically mean:

> Every relevant condition has been validated.

***

### Validated

Validated means that an implemented property has been exercised against defined tests, scenarios, checks, or evaluation conditions.

Validation connects:

**Property**\
↓\
**Test Condition**\
↓\
**Expected Result**\
↓\
**Observed Behavior**

Current Admission Kernel MVP validation includes several evidence forms rather than one universal test number.

They include:

**Application test inventory**\
26 tests

**Release-builder compatibility execution**\
26/26 PASS

**Standalone core verification**\
49/49 PASS

**Six execution scenarios**\
6/6 observed as expected

**Public evidence verification**\
113/113 PASS

These numbers refer to different validation layers and must not be added together or treated as equivalent units.

***

### Independently Reproduced

Independently Reproduced means that the relevant implementation behavior or research result has been reproduced outside the originating implementation or research team under an independently controlled environment.

This is stronger than:

* publishing source-derived evidence,
* publishing a verifier,
* publishing test output,
* publishing schemas,
* or allowing another reader to verify signatures and hashes.

The current official status remains:

> **Independent External Reproduction — Not yet completed**

***

### Publicly Recheckable Is Not a Fifth Evidence State

Public Proof v2.0 makes the disclosed evidence package independently downloadable and mechanically recheckable.

That is an important increase in evidence quality.

It does not create a fifth canonical evidence state between Validated and Independently Reproduced.

Instead:

> **Public recheckability is a property of the disclosed evidence.**

The four-state evidence model remains unchanged.