> 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/4.-governance-objects/4.-governance-objects.md).

# 4. Governance Objects

LPP expresses governance through structured objects rather than through unbound natural-language approval.

This is necessary because consequential AI execution may pass through multiple models, agents, tasks, tools, systems, and time states before an external effect occurs.

A statement such as:

```
"Yes, you may proceed."
```

is not sufficient by itself to establish:

* who granted authority,
* what was authorized,
* what scope applies,
* how long authority remains valid,
* whether authority has been revoked,
* whether the current objective still matches the authorized objective,
* what exact execution was permitted,
* or why the resulting action was admitted.

The governance architecture therefore separates several objects with different responsibilities.

The canonical relationship is:

```
Authority
        ↓
Authorized Intent
        ↓
Authority–Intent Binding
        ↓
Action / Intent Commitment
        ↓
Admission
        ↓
Execution Permit
        ↓
Execution
        ↓
Admission Artifact
```

Each object answers a different question.

| Governance Object           | Primary Question                                                 |
| --------------------------- | ---------------------------------------------------------------- |
| Authority Object            | What legitimate authority existed?                               |
| Human-Authorized Intent     | What did that authority actually authorize?                      |
| Authority–Intent Binding    | Which authority is bound to which authorized meaning?            |
| Canonical Intent Commitment | What normalized intent is being preserved across the trajectory? |
| Execution Intent            | What concrete action is now being proposed?                      |
| Execution Permit            | What constrained execution is allowed now?                       |
| Admission Artifact          | Why was the action admitted or denied under the governing state? |

These objects must not be treated as interchangeable.

A Permit is not an Authority Object.

An Authority Object is not Human-Authorized Intent.

An Admission Artifact is not an authorization source.

A valid object at one stage does not eliminate the need for the objects and checks required at later stages.