> 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.1-kernel-role.md).

# 5.1 Kernel Role

The canonical role of the LPP Admission Kernel is:

> **Layer 0 Constitutional Admissibility Kernel**

It determines whether a specific AI-triggered action possesses the legitimacy required to proceed toward downstream execution governance.

The kernel is not:

* a chatbot safety filter,
* a model-alignment mechanism,
* a task orchestrator,
* a general policy engine,
* an identity provider,
* an audit log,
* a physical safety controller,
* or a post-event compliance system.

These systems may exist around it.

They do not perform the same governance function.

#### Position in the Architecture

The canonical position is:

```
Authority Object
+
Human-Authorized Intent
        ↓
Authority–Intent Binding
        ↓
Semantic & Task Governance
        ↓
Action Candidate
        ↓
Intent / Verification Evidence
        ↓
LPP Admission Kernel
        ↓
ADMIT | DENY | DEFER | COLLAPSE
```

The kernel consumes governance-relevant state.

It does not create legitimate human authority from model reasoning.

#### Layer 0 Function

Layer 0 evaluates legitimacy.

Layer 1 evaluates and enforces runtime permission.

The relationship is:

```
Layer 0
Is this action admissible?

        ↓

Layer 1
Is this admissible action permitted
under current runtime constraints?

        ↓

Execution
Perform the permitted action.
```

Layer 1 may impose additional restrictions.

It may not expand the legitimate boundary produced by Layer 0.

#### Kernel Invariants

The hardened Authority Layer model identifies several core invariants:

```
No execution without valid authority.

No silent scope expansion.

No persistence under revocation.

No circular delegation.

No self-authorization by the Execution Plane.

No execution under undefined governance state.
```

These invariants express the kernel's role as a structural control boundary rather than a recommendation system.

***

###