> 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/10.-research-and-publications/10.3-paper-2-lpp-admission-kernel.md).

# 10.3 Paper 2 — LPP Admission Kernel

#### Publication

**LPP Admission Kernel: Formal Operational Semantics for Layer 0 AI-Triggered Action Admissibility**

Author: Jason Liao\
Publication: Zenodo\
Version: v0.2\
Publication Date: June 11, 2026\
DOI:

```
10.5281/zenodo.20726851
```

#### Research Question

> **How does Layer 0 actually decide?**

Paper 1 establishes that constitutional admissibility is necessary.

Paper 2 converts that principle into an operational model.

The central object becomes:

> **LPP Admission Kernel**

#### Formal Kernel

The paper defines:

```
Admit₀(AR, G, Σ) → AD
```

where:

* `AR` = Admission Request,
* `G` = governing admissibility constitution or rules,
* `Σ` = current governance / authority state,
* `AD` = admissibility decision.

This transforms Layer 0 from a conceptual boundary into a decision model.

#### Minimal Object Model

Paper 2 introduces operational objects including:

* Admission Requests,
* Authority Objects,
* Responsibility Chains,
* Revocation States,
* Risk Tiers,
* Admissibility Decisions,
* Execution Permits,
* and Collapse Reasons.

These objects establish the minimum semantic structure required for implementation and comparison.

#### Authority Lifecycle

The paper formalizes authority as stateful rather than permanent.

The kernel must account for conditions such as:

* authority existence,
* validity,
* expiry,
* revocation,
* responsibility continuity,
* and scope.

This creates the operational foundation later expanded by Paper 4.

#### Risk-Tiered Admissibility

Paper 2 introduces proportional governance based on consequence or risk.

The exact classification model later evolves into the canonical LPP T0–T4 structure.

The underlying principle remains:

> **Increasing consequence may require stronger admission conditions.**

#### Decision Model

Paper 2 develops the four Layer 0 decision classes:

```
ADMIT
DENY
DEFER
COLLAPSE
```

and the restrictive priority:

```
COLLAPSE
>
DENY
>
DEFER
>
ADMIT
```

This makes admissibility non-compensatory.

A structural failure cannot be outweighed by favorable confidence or utility elsewhere.

#### Fail-Closed Semantics

The paper explicitly rejects execution based on unresolved Layer 0 state.

Examples include:

* silence,
* timeout,
* unavailable authority,
* incomplete responsibility chain,
* malformed admissibility state,
* and unverifiable Permit.

The governing rule is:

```
Unresolved Layer 0 State
≠
Permission
```

#### Execution Permit

Paper 2 introduces the constrained Execution Permit as the interface between Layer 0 and Layer 1.

The architecture becomes:

```
Admission Kernel
        ↓
ADMIT
        ↓
Execution Permit
        ↓
Layer 1
        ↓
Execution
```

#### Layer 0 / Layer 1 Interface

The paper establishes one of the central operational boundaries of LPP:

> Layer 0 determines admissibility.

> Layer 1 enforces constrained execution.

Layer 1 may restrict an admitted action further.

It may not manufacture legitimacy or expand the authority granted by Layer 0.

#### Failure Modes

Paper 2 provides a failure taxonomy covering conditions such as:

* unavailable Admission Kernel,
* authority-resolution timeout,
* malformed request,
* malformed Authority Object,
* signature failure,
* unavailable revocation state,
* incomplete responsibility chain,
* risk uncertainty,
* Permit failure,
* scope mismatch,
* boundary mutation,
* unavailable human approval,
* policy-origin failure,
* incomplete delegation,
* and execution-environment mismatch.

This moves LPP toward implementation-ready semantics.

#### Boundary of the Paper

Paper 2 does not claim to provide a complete production system.

Its purpose is to define the minimum operational semantics required for Layer 0 to be:

* implemented,
* compared,
* audited,
* and eventually standardized.

#### Research Role

Paper 2 therefore establishes:

```
The Operational Admission Layer
```

Paper 1 explains **why Layer 0 exists**.

Paper 2 explains **how Layer 0 can decide**.