> 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/14.-appendix/14.3-authority-lifecycle-state-machine.md).

# 14.3 Authority Lifecycle State Machine

Canonical Authority Object lifecycle:

```
                    mint conditions satisfied
        ┌─────────────────────────────────────┐
        │                                     ▼
   ┌──────────┐                          ┌──────────┐
   │ UNMINTED │                          │  MINTED  │
   └──────────┘                          └────┬─────┘
        ▲                                     │
        │ mint failure                        │
        └─────────────────────────────────────┘
                                              │
                    ┌─────────────────────────┼─────────────────────┐
                    │                         │                     │
                    ▼                         ▼                     ▼
               ┌─────────┐              ┌─────────┐           ┌─────────┐
               │ INVALID │              │ EXPIRED │           │ REVOKED │
               └─────────┘              └─────────┘           └─────────┘
```

Canonical status domain:

```
UNMINTED
MINTED
INVALID
EXPIRED
REVOKED
```

| State    | Meaning                                                    |
| -------- | ---------------------------------------------------------- |
| UNMINTED | No valid Authority Object has been instantiated            |
| MINTED   | Authority Object exists and may be evaluated for admission |
| INVALID  | Object has lost required validity                          |
| EXPIRED  | Validity window has ended                                  |
| REVOKED  | Authority has been withdrawn                               |

Important distinction:

```
MINTED
≠
Automatically ADMIT
```

A MINTED Authority Object must still satisfy:

* scope,
* signatures,
* validity,
* revocation,
* class,
* policy,
* intent,
* verification,
* and applicable invariants.

### Decision-Mapping Boundary

Published Authority Object research contains both lifecycle-level collapse language and a later explicit failure table mapping several lifecycle failures to DENY.

The state machine itself therefore does not assign the final GitBook decision code.

See:

> **Appendix 14.14 — Decision & Failure Mapping**

for the current normalization.

This avoids silently erasing version-local research semantics.