> 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.2-paper-1-constitutional-admissibility.md).

# 10.2 Paper 1 — Constitutional Admissibility

#### Publication

**Lingua Pactum Protocol: Constitutional Admissibility for AI-Triggered Language and Action**

Author: Jason Liao\
Publication: Zenodo\
Version: v0.1\
Publication Date: May 25, 2026\
DOI:

```
10.5281/zenodo.20373354
```

#### Research Question

> **Why is an upstream Layer 0 required before runtime governance?**

Paper 1 establishes the foundational distinction between:

```
Runtime Governance
```

and:

```
Constitutional Admissibility
```

Runtime governance asks whether an already-formed request should be permitted under operational policy.

Constitutional admissibility asks whether the request possesses sufficient legitimacy to become a valid execution candidate in the first place.

#### Core Problem

AI-generated language increasingly acts as an interface to:

* tool calls,
* workflows,
* transactions,
* system mutation,
* delegated tasks,
* and other real-world effects.

Existing security and governance systems may successfully determine that:

```
Request R complies with policy P.
```

But that does not establish:

```
Request R has a legitimate authority basis.
```

The first paper therefore identifies an upstream governance gap.

#### Core Contribution

The central claim is:

> **AI-triggered execution requires an upstream constitutional admissibility layer because runtime control alone cannot establish the legitimacy of the control boundary it enforces.**

The paper contributes several foundational ideas.

**Constitutional Admissibility**

An action must possess sufficient legitimate grounding before it enters downstream execution governance.

**Layer 0 vs Runtime Governance**

The paper distinguishes:

```
Layer 0
Constitutional Admissibility

from

Layer 1
Runtime Policy / Authorization
```

**Minimal Admissibility Model**

The paper introduces a minimal formal model of the AI-triggered action and governance state and defines a Layer 0 admissibility predicate.

The model establishes that admissibility depends on mandatory conditions such as:

* valid authority,
* bounded scope,
* responsibility traceability,
* revocation clearance,
* constitutional preservation,
* and human-sovereign origin.

**Admissibility Collapse**

Paper 1 distinguishes ordinary policy refusal from a deeper failure of constitutional legitimacy.

This becomes the basis of the later:

```
COLLAPSE
```

decision state.

**Policy Compliance Is Not Legitimacy**

One of the paper's most important conclusions is:

> **Policy pass does not imply constitutional admissibility.**

A system may be:

* authenticated,
* policy-compliant,
* technically permitted,
* logged,
* and executable,

while still lacking a valid legitimacy basis.

#### Boundary of the Paper

Paper 1 defines **why Layer 0 must exist**.

It does not yet fully specify:

* the operational Admission Kernel,
* complete Authority Object structure,
* financial-domain application,
* trajectory-level intent preservation,
* or the executable reference architecture.

Those questions become the subjects of later papers.

#### Research Role

Paper 1 therefore establishes:

```
The Constitutional Layer
```

It provides the intellectual foundation for everything that follows.