> 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/6.-intent-and-trajectory-governance/6.10-authority-object-vs-human-intent.md).

# 6.10 Authority Object vs Human Intent

Authority Object and Human Intent H must remain separate because they establish different dimensions of legitimacy.

#### Authority Object — Authority Validity

The Authority Object answers questions such as:

* Who issued authority?
* Who is the subject?
* What scope applies?
* Is the authority valid?
* Has it expired?
* Has it been revoked?
* What delegation constraints apply?
* What consequence requirements apply?

This is **authority validity**.

#### Human Intent H — Semantic Legitimacy

Human Intent H answers:

> **What did the authority actually authorize the system to accomplish?**

This is the semantic side of legitimacy.

#### Why Valid AO Alone Is Insufficient

Consider:

```
AO = valid
AO.status = MINTED
AO.revoked = false
AO within validity window
```

That establishes that a legitimate authority object exists.

It does not prove:

```
Current action preserves H.
```

Therefore:

```
Valid(AO)
⇏
TrajectoryAdmissible
```

A fuller conceptual condition is:

```
AuthorityValid(AO)
∧
IntentPreserved(T, H)
∧
ScopeValid
∧
RevocationClear
∧
other mandatory predicates
```

before the Admission Kernel can reach the applicable positive decision.

This is an explanatory representation of the public architecture; the full formal model remains defined in the published research.

#### Two Different Failure Modes

Authority can fail while intent remains understandable:

```
The requested objective is clear,
but the authority has been revoked.
```

Intent can fail while authority remains valid:

```
The Authority Object remains valid,
but the current action no longer reflects H.
```

Both block ordinary inheritance of execution legitimacy.

#### Canonical Relationship

```
Authority Object
        ↓
Who / under what conditions?

Human Intent H
        ↓
What meaning was authorized?

Authority–Intent Binding
        ↓
Which authority authorized which meaning?

Semantic Verification
        ↓
Is that meaning still preserved?

Admission Kernel
        ↓
Is the action admissible now?
```

This separation is one of the central architectural refinements of GitBook v2.0.