> 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/2.lpp-positioning/2.5-what-lpp-does-not-do.md).

# 2.5 What LPP Does Not Do

Clear protocol boundaries are necessary to prevent LPP from becoming an undefined claim over all AI governance.

LPP does **not** replace adjacent technical systems.

#### LPP Does Not Replace IAM

Identity and Access Management systems remain responsible for identifying principals and managing access relationships.

LPP may depend on trusted identity information.

It does not replace identity infrastructure.

#### LPP Does Not Replace Policy Engines

Policy engines determine whether requests satisfy declared operational policy.

LPP operates upstream of this question.

It does not replace runtime policy evaluation.

#### LPP Does Not Replace Cybersecurity

LPP is not a complete cybersecurity framework.

It does not replace:

* network security,
* endpoint protection,
* vulnerability management,
* sandboxing,
* intrusion detection,
* cryptographic key protection,
* security monitoring,
* or conventional security controls.

Its concern is constitutional action legitimacy.

#### LPP Does Not Replace Functional Safety

For physical AI and robotics, LPP does not replace:

* collision avoidance,
* motion safety,
* emergency-stop systems,
* fail-safe controllers,
* safety PLCs,
* real-time physical constraints,
* or certified functional safety mechanisms.

LPP governs the upstream authority question.

A robot may be physically able to enter an area safely while still lacking authority to enter it.

Conversely, legitimate authority does not prove that the physical action is mechanically safe.

#### LPP Does Not Replace Model Alignment

LPP does not claim to guarantee that a model is:

* truthful,
* harmless,
* aligned,
* unbiased,
* robust,
* or generally correct.

A well-aligned model may still lack legitimate authority.

An imperfect model may still operate within a strongly constrained execution architecture.

These are different governance problems.

#### LPP Does Not Replace Task Orchestration

LPP does not manage general task decomposition, context routing, task scheduling, workflow construction, or module orchestration.

Within Mind Universe, these functions belong primarily to Jarvis / TaskChain and related governance modules.

#### LPP Does Not Replace Physical Safety Controllers

Constitutional admissibility is upstream of actuation.

Real-time physical safety remains a responsibility of the appropriate downstream systems.

#### Additional Non-Claims

LPP should also not be interpreted as independently guaranteeing:

* business utility,
* model correctness,
* general regulatory compliance,
* universal AI safety,
* or production security.

LPP defines a specific governance boundary:

> **The legitimacy qualification of AI-triggered action before downstream execution governance.**