> 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/13.-reference-and-governance/13.6-public-controlled-confidential-disclosure-matrix.md).

# 13.6 Public / Controlled / Confidential Disclosure Matrix

LPP separates **disclosure level** from **licensing rights**.

The canonical disclosure model contains four levels:

```
P0 — Public Normative
P1 — Public Technical
P2 — Controlled Technical
P3 — Confidential / Secret
```

***

#### P0 — Public Normative

P0 contains the material required for the public to understand what LPP claims and what its constitutional boundaries are.

P0 may include:

* Constitution,
* core principles,
* canonical definitions,
* Layer 0 / Layer 1 distinction,
* governance invariants,
* object relationships,
* protocol boundaries,
* decision semantics,
* and normative non-compensatory principles.

The objective is:

> **The constitutional rules cannot depend on undisclosed interpretation.**

***

#### P1 — Public Technical

P1 contains technical information needed for meaningful inspection, research, interoperability, testability, and eventual external reproduction.

P1 may include:

* Authority Object grammar,
* research-defined intent objects,
* public Execution Permit schemas,
* public Admission Artifact schemas,
* `ADMIT / DENY / DEFER / COLLAPSE` semantics,
* state transitions,
* revocation semantics,
* interface contracts,
* non-sensitive failure codes,
* test vectors,
* conformance material,
* reference-implementation material,
* benchmarks,
* and public validation results.

The website and GitBook may therefore disclose more technical detail than earlier “public-safe” editions.

This is deliberate.

External reproducibility requires sufficient public technical material.

***

#### P2 — Controlled Technical

P2 contains implementation details that may be useful for:

* partners,
* research collaborators,
* evaluation teams,
* enterprise integration,
* or controlled technical review,

but should not necessarily be broadly published.

Examples include:

* production threshold calibration,
* institution-specific risk matrices,
* production quorum weights,
* operational escalation rules,
* production key-management architecture,
* deployment topology,
* proprietary enterprise adapters,
* non-public anti-bypass controls,
* security hardening,
* private orchestration logic,
* and commercial integration configurations.

P2 material may be shared through:

```
Controlled Evaluation
Partner Access
NDA
License
Research Agreement
```

as appropriate.

***

#### P3 — Confidential / Secret

P3 contains information that should not be publicly disclosed.

Examples include:

* private keys,
* credentials,
* live customer configurations,
* customer data,
* production access paths,
* operational security secrets,
* materially enabling bypass knowledge,
* confidential incident records,
* and similar protected operational material.

P3 exists because transparency does not require publishing the information needed to compromise the system being made transparent.

***

#### Disclosure ≠ License

This distinction is fundamental:

```
Public
≠
Unrestricted Commercial Use
```

A P0 or P1 artifact may be publicly readable while remaining governed by a specific copyright or license.

Likewise, P2 classification describes disclosure access.

It does not itself define a commercial license.