> 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.5-execution-intent.md).

# 4.5 Execution Intent

The **Execution Intent** represents the concrete action that the system proposes to perform.

It is the object evaluated against authority, scope, policy state, intent preservation, consequence requirements, and other applicable admission predicates.

The Authority Objects research represents an execution intent conceptually as:

```
E = ⟨
    subject,
    action,
    target,
    parameters,
    scope,
    class,
    intent_hash,
    time
⟩
```

The current Admission Kernel MVP uses a minimal executable form:

```
ExecutionIntent {
    intent_id
    principal_id
    function
    target
    params_c14n
    intent_hash
    timestamp
}
```

These representations serve different levels of abstraction.

The first expresses the broader protocol-level execution candidate.

The second is the current MVP's minimal executable structure.

#### Execution Intent Is Concrete

Human-Authorized Intent may express:

```
Restore service on the affected production system
without modifying unrelated infrastructure.
```

Execution Intent may represent:

```
function:
    restart_service

target:
    production:service:A

parameters:
    {...}
```

The Admission Kernel must determine whether the concrete proposed operation remains compatible with the legitimate upstream authority and intent.

#### Canonicalization

The current MVP normalizes parameters before hashing.

This is necessary because logically equivalent structured input should not produce accidental ambiguity through irrelevant formatting differences.

A simplified flow is:

```
Function + Target + Parameters
        ↓
Canonical Representation
        ↓
Intent Hash
```

#### Intent Hash

The execution-intent hash binds downstream authorization to a specific execution proposal.

This prevents a Permit issued for one intent from being reused for a materially different request.

Conceptually:

```
Permit.intent_hash
=
H(Execution Intent)
```

#### Execution Intent Does Not Create Authority

The Execution Plane may propose an Execution Intent.

It may not interpret the existence of that intent as authorization.

```
Execution Intent
=
proposal for evaluation

not

authority to execute
```