> 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.6-mandatory-re-admission.md).

# 6.6 Mandatory Re-Admission

The canonical trajectory rule is:

> **Material Mutation ⇒ Re-Admission**

This is one of the central constraints introduced by trajectory-level intent governance.

It means that once a material mutation occurs, the resulting action may not simply inherit the earlier admission state.

The changed action must return to the admission process.

#### Why Re-Admission Is Necessary

Without re-admission, an agent could obtain legitimate authority once and then gradually transform the task while continuing to rely on that original approval.

Conceptually:

```
Authorized Task A
        ↓
ADMIT
        ↓
A'
        ↓
A''
        ↓
A'''
        ↓
Materially different Action B
        ↓
execute under original approval
```

This would convert bounded authority into an implicit open-ended delegation.

Re-admission prevents that.

#### Re-Admission Flow

A simplified public flow is:

```
Previously Admitted Trajectory
        ↓
Material Mutation Detected
        ↓
Previous admission is not sufficient
for the mutated action
        ↓
Update Action Candidate / Intent State
        ↓
Semantic Verification
        ↓
LPP Admission Kernel
        ↓
New admission decision
```

#### Re-Admission Is Not Automatic Denial

Material Mutation does not necessarily mean the new action is illegitimate.

It means the new action requires a fresh governance decision.

The legitimate authority may approve the changed action.

Additional scope may be granted.

A new Authority–Intent Binding may be created.

The resulting action may eventually receive `ADMIT`.

But it must not obtain legitimacy merely through inheritance.

#### Re-Admission and Execution Permits

An Execution Permit is intent-bound and scope-bound.

A materially changed action cannot assume that an earlier Permit authorizes the new execution intent.

The new action must satisfy the applicable admission and Permit-minting path.