> 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/1.constitutional-foundation/1.6-anti-bypass-principles.md).

# 1.6 Anti-Bypass Principles

The constitutional layer is meaningless if lower layers can bypass it.

Anti-bypass therefore protects not only individual execution decisions but the integrity of the governance architecture itself.

#### No Self-Authorization

The system requesting execution must not be able to create its own legitimacy.

This principle requires separation between:

```
Proposal
and
Authorization

Execution
and
Legitimacy
```

An agent may create an execution request.

The request cannot become legitimate solely because the agent requests it.

#### No Legitimacy Creation by the Execution Plane

The Execution Plane exists to execute actions that have already satisfied required upstream governance conditions.

It may not legitimately:

* mint its own authority,
* restore revoked authority,
* expand scope,
* rewrite authorization history,
* redefine constitutional conditions,
* or issue itself a valid Permit.

This is why later architecture separates:

```
Control Plane
≠
Execution Plane
```

The separation is not only a security convenience.

It derives from the constitutional prohibition against self-authorization.

#### Failed Authority Cannot Be Compensated Downstream

A constitutional failure cannot be repaired merely by stronger downstream signals.

If required authority is absent or invalid:

```
High confidence
+
Low operational risk
+
Valid tool permission
+
High expected utility
+
Successful policy evaluation
```

still does not create constitutional legitimacy.

Therefore:

> **Failed constitutional predicates are non-compensatory.**

This principle prevents governance from collapsing into optimization.

#### Efficiency Does Not Override Governance

Efficiency pressure is a recurring bypass vector.

A system may attempt to justify weaker governance because:

* human review is slow,
* revocation checks add latency,
* admission reduces throughput,
* independent verification is expensive,
* or execution is time-sensitive.

The Constitution does not treat operational efficiency as a source of legitimacy.

Optimization may occur inside constitutional boundaries.

It may not erase them.

#### Human-Auditable Semantics

High-impact AI collaboration must remain governable through human-auditable semantic structures.

AI systems must not create an opaque coordination layer that effectively bypasses:

* responsibility,
* authority,
* attribution,
* or governance inspection.

This principle provides the constitutional basis for later SCSP and Anti-SCSP mechanisms.

#### Continuous Trajectory Governance

Statement-level compliance alone is insufficient for systems whose meaning changes over time.

A sequence may contain individually plausible steps while producing a trajectory that no longer corresponds to the original authority.

Therefore anti-bypass governance must account for:

```
Local compliance
≠
Trajectory legitimacy
```

This constitutional concern later becomes formalized through intent preservation, Semantic Verification, Material Mutation, and mandatory re-admission.