> 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.13-public-interface-summary.md).

# 14.13 Public Interface Summary

The following interfaces represent the current **MVP reference implementation surface**, not a finalized universal LPP wire protocol.

***

### Control Plane Interfaces

#### Propose Execution Intent

```
POST /intent/propose
```

Conceptual input:

```
Execution Intent
+
Current Authority / Scope State
```

Output:

```
Permit
```

or:

```
Deny Result
```

***

#### Revoke Authority

```
POST /authority/revoke
```

Purpose:

```
Update authority to
non-executable revoked state.
```

***

#### Retrieve Admission Artifact

```
GET /artifact/{id}
```

Purpose:

```
Retrieve evidence required
for reconstruction.
```

***

#### Retrieve Authority State

```
GET /authority/{id}
```

Purpose:

```
Retrieve authority snapshot
or reconstruction material.
```

***

#### Retrieve Scope State

```
GET /scope/{id}
```

Purpose:

```
Retrieve scope envelope
or reconstruction material.
```

***

### Execution Plane Interface

#### Execute

```
POST /execute
```

Input:

```
Execution Intent
+
Execution Permit
```

Internal mandatory sequence:

```
VerifyPermit()
        ↓
Execute only if valid
```

Output:

```
Execution Result
+
Artifact Reference
```

***

### Public Interface Boundary

These endpoints demonstrate the current reference implementation architecture.

They are not yet claimed as:

* a universal IETF-style interface,
* final interoperable wire format,
* mandatory REST design,
* or complete future conformance API.

An implementation may use:

* RPC,
* message bus,
* local library interface,
* middleware,
* gateway,
* or another transport

while preserving the same semantic control boundary.