> 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/11.-public-proof-and-validation/11.6-current-decision-coverage.md).

# 11.6 Current Decision Coverage

The canonical Layer 0 decision model contains:

* `ADMIT`
* `DENY`
* `DEFER`
* `COLLAPSE`

The current executable MVP implements a narrower decision domain.

| Decision   | Protocol Status | Current MVP               | Current Validation      |
| ---------- | --------------- | ------------------------- | ----------------------- |
| `ADMIT`    | Specified       | Implemented               | Validated               |
| `DENY`     | Specified       | Implemented               | Validated               |
| `DEFER`    | Specified       | Not currently implemented | Not currently validated |
| `COLLAPSE` | Specified       | Not currently implemented | Not currently validated |

This is also the status declared in Public Proof v2.0.

### ADMIT

The MVP demonstrates the valid governed execution path:

**Valid Governance State**\
↓\
**ADMIT**\
↓\
**Execution Permit**\
↓\
**Execution**

***

### DENY

The MVP demonstrates multiple deterministic denial paths.

Examples include:

* no Permit,
* invalid Permit signature,
* scope violation,
* replay,
* revocation,
* expiration,
* policy mismatch,
* and intent mismatch.

Operational reason-code details are centralized in Chapter 13.4.

***

### DEFER

DEFER exists in the Layer 0 protocol model for unresolved mandatory conditions.

Examples may include:

* missing evidence,
* incomplete signatures,
* pending verification,
* unresolved consensus,
* or mandatory review not yet completed.

The current final MVP does not claim an implemented DEFER path.

***

### COLLAPSE

COLLAPSE represents a constitutional or structural failure state.

It is stronger than an ordinary current-state rejection.

The current final MVP does not claim an implemented COLLAPSE path.

***

### Protocol Completeness vs Prototype Completeness

The correct interpretation is:

> **Protocol Completeness ≠ MVP Completeness**

This is not an inconsistency.

It is the declared implementation boundary.