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

# 14.6 Revocation Flow

Canonical revocation relationship:

```
Authority MINTED
        ↓
Revocation Trigger
        ↓
Revocation State Updated
        ↓
Authority REVOKED
        ↓
No new ADMIT under that authority
```

Extended execution-boundary relationship:

```
Authority ACTIVE
        ↓
ADMIT
        ↓
Permit Issued
        ↓
Authority Revoked
        ↓
Execution Attempt
        ↓
Gate-Time Authority / Revocation Check
        ↓
BLOCK
```

Representative revocation triggers from current Authority Object research include:

* explicit issuer withdrawal,
* subject withdrawal,
* jurisdiction withdrawal,
* identity compromise,
* evidence invalidation,
* policy change,
* scope violation,
* security incident,
* expiration,
* cross-domain legal conflict,
* or superseding authority.

#### Current MVP Evidence

Current MVP validation demonstrates:

```
Revoke authority
        ↓
attempt later execution
        ↓
DENY / BLOCK
```

It does **not** establish comprehensive continuous mid-execution revocation across every distributed deployment.

That stronger property remains part of the Continuous Admissibility model.