> 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.6-revocation.md).

# 5.6 Revocation

Revocation is the mechanism by which previously valid authority ceases to support execution.

It is a constitutional requirement because authority without effective revocation becomes one-way power.

The core rule is:

```
Revoked Authority
⇒
No new ADMIT under that authority
```

#### Revocation State

The formal operational model represents revocation state with values such as:

```
Active
Suspended
Expired
Revoked
Unknown
Conflicting
```

The critical principle is:

> **Unknown must not be treated as Active where the governing risk or consequence profile requires verified revocation state.**

Unavailable revocation information is not permission.

#### Revocation Triggers

Published LPP specifications identify triggers such as:

* jurisdiction withdrawal,
* evidence invalidation,
* identity compromise,
* cross-domain conflict,
* superseding authority,
* or expiration.

Specific institutional profiles may define additional legitimate triggers.

#### Before Execution

If revocation occurs before the governed action executes:

```
Authority valid at admission
        ↓
Authority revoked
        ↓
Execution not yet occurred
        ↓
Previous authority must not be assumed sufficient
```

The corresponding Permit may need to be rejected or invalidated according to the applicable execution profile.

#### During Execution

For long-running or interruptible execution, higher-assurance profiles may apply **continuous admissibility**.

The hardened security invariant is:

```
∀t ∈ [T₀, T₁]

AuthorityState(t) = ACTIVE
```

otherwise:

```
Execution halts.
```

This stronger continuous model is discussed in Chapter 8.

#### Revocation Propagation

Revocation is only meaningful if the execution boundary can learn that authority changed.

Production profiles therefore need an appropriate revocation-propagation mechanism or bounded validity model.

A stale credential must not become a way to preserve authority indefinitely after revocation.

#### Revocation Is Not Post-Hoc Audit

The purpose of revocation is not merely to record:

```
Authority was later revoked.
```

It is to prevent invalid authority from continuing to produce consequential action.