> 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.3-authority-intent-binding.md).

# 4.3 Authority–Intent Binding

An **Authority–Intent Binding** connects a specific Authority Object to the specific authorized meaning governed by that authority.

Conceptually:

```
AO ↔ H
```

where:

```
AO = Authority Object
H  = Human-Authorized Intent
```

The binding answers:

> **Which authority authorized which meaning?**

This relationship is necessary because an Authority Object must not become a reusable credential for semantically unrelated objectives.

#### Why Binding Is Required

Without binding, a system could incorrectly reason:

```
Authority A is valid.
        ↓
Therefore any action proposed by the associated agent
may rely on Authority A.
```

LPP rejects this inference.

The correct relationship is closer to:

```
Authority A
        ↓
authorizes
        ↓
Intent H
```

A later action must therefore remain within both:

* the authority boundaries of `AO`,
* and the authorized semantic boundaries of `H`.

#### Canonical Public References

The current GitBook architecture defines the public binding relationship through three core references:

```
authority_object_ref
human_intent_ref
authorized_intent_hash
```

Conceptually:

```
AuthorityIntentBinding {
    authority_object_ref
    human_intent_ref
    authorized_intent_hash
}
```

This is an architectural public representation.

The complete schema and signing requirements belong to the relevant public technical specification / Appendix schema.

#### authority\_object\_ref

Identifies the Authority Object on which legitimacy depends.

The binding must not silently migrate to another authority source without governance review.

#### human\_intent\_ref

Identifies the corresponding authorized-intent record.

This makes it possible to reconstruct what legitimate meaning was associated with the authority.

#### authorized\_intent\_hash

Provides a stable cryptographic commitment to the authorized intent representation used by the system.

Its purpose is to prevent silent semantic substitution after authority has been bound.

Conceptually:

```
Authority Object
        +
Human-Authorized Intent
        ↓
authorized_intent_hash
        ↓
Authority–Intent Binding
```

#### Binding Does Not Guarantee Permanent Semantic Equivalence

The binding establishes the authorized starting relationship.

It does not guarantee that every future agent transformation remains equivalent.

An evolving trajectory may:

* reinterpret,
* expand,
* narrow,
* combine,
* delegate,
* substitute targets,
* or otherwise materially mutate the objective.

That is why later Semantic Verification is required.

Authority–Intent Binding establishes:

```
What authority was bound to what intent.
```

Semantic Verification later evaluates:

```
Whether the evolving trajectory still preserves that intent.
```