> 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/11.-public-proof-and-validation/11.10-conformance-profile.md).

# 11.10 Conformance Profile

A complete LPP public conformance specification is **not currently finalized**.

Public Proof v2.0 materially improves technical inspectability.

It does not transform the current evidence verifier into a protocol conformance suite.

Therefore:

> **Public Evidence Verification ≠ LPP Conformance Testing**

### Purpose of Conformance

A future conformance profile should answer:

> Does an implementation behave according to the canonical public LPP semantics for the properties it claims to implement?

This differs from asking:

> Is the implementation generally secure?

or:

> Is the implementation production-certified?

Conformance is protocol-specific.

***

### Candidate Baseline Properties

A future baseline conformance suite would likely need to test properties such as:

**No Permit**\
→ No governed execution

**Invalid Signature**\
→ Execution blocked

**Out-of-Scope Action**\
→ Execution blocked

**Expired Permit**\
→ Execution blocked

**Expired / inactive Authority**\
→ Execution blocked

**Revoked Authority**\
→ Execution blocked

**Replay**\
→ Execution blocked

**Intent Binding**\
→ Execution Intent remains consistent with the Permit

**Policy Binding**\
→ governing policy state remains consistent with the Permit

**Evidence Reconstruction**\
→ claimed execution basis can be reconstructed

These candidate properties are derived from the current MVP and technical specifications.

They do not yet constitute a separately published final LPP certification regime.

***

### Conformance May Be Profile-Specific

Logical CP / EP separation and higher-assurance physical enforcement are not equivalent deployment classes.

Future conformance may therefore distinguish:

> **Core Protocol Conformance**

from:

> **Higher-Assurance Deployment Conformance**

and potentially:

> **Domain-Specific Conformance**

for areas such as finance, cyber operations, or Physical AI.

***

### Conformance ≠ Certification

Even when available:

> **LPP Conformant**

would not automatically mean:

> production-secure in every environment

or:

> regulator-approved.

Protocol conformance and external certification remain different assurance layers.