> 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/5.-lpp-admission-kernel/5.-lpp-admission-kernel.md).

# 5. LPP Admission Kernel

The **LPP Admission Kernel** is the Layer 0 mechanism that operationalizes constitutional admissibility.

Its purpose is to determine whether an AI-triggered Action Candidate has sufficient legitimate authority, preserved scope, valid lifecycle state, revocation clearance, required evidence, and applicable governance conditions to proceed toward execution.

The Admission Kernel operates before ordinary runtime authorization.

It does not ask only:

> **Does runtime policy allow this action?**

It asks first:

> **Is this action constitutionally qualified to become an execution candidate at all?**

The formal research model expresses the kernel as:

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

where:

* `AR` = Admission Request,
* `G` = governance constitution or admissibility rule set,
* `Σ` = current authority and governance state,
* `AD` = admissibility decision.

The decision domain is:

```
AD ∈ {
    Admit(EP),
    Deny(r),
    Defer(r),
    Collapse(r)
}
```

where:

* `EP` = Execution Permit,
* `r` = reason code.

The kernel therefore sits at the transition:

```
Action Candidate
        ↓
Layer 0 Admission
        ↓
ADMIT | DENY | DEFER | COLLAPSE
        ↓
ADMIT only
        ↓
Execution Permit
        ↓
Layer 1 / Execution Boundary
```

Its governing principle is:

> **Authority before execution.**

And its enforcement principle is:

> **No unresolved admissibility state may silently become execution permission.**