> 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.2-symbols.md).

# 13.2 Symbols

Published LPP papers were written at different stages of the research program.

Some symbols are therefore paper-specific.

GitBook v2.0 does **not** retroactively rewrite the notation inside published papers.

Instead, this section establishes a canonical public reading convention.

#### Core Layer Symbols

| Symbol | Meaning                                                                           |
| ------ | --------------------------------------------------------------------------------- |
| `L0`   | Layer 0 Constitutional Admissibility                                              |
| `L1`   | Layer 1 Runtime Policy / Authorization                                            |
| `AR`   | Admission Request                                                                 |
| `AO`   | Authority Object                                                                  |
| `AC`   | Action Candidate                                                                  |
| `RC`   | Responsibility Chain                                                              |
| `RV`   | Revocation State                                                                  |
| `AD`   | Admissibility Decision                                                            |
| `G`    | Governance state, constitution, or applicable admissibility rule context          |
| `Σ`    | Current authority and governance state in Paper 2 notation                        |
| `⊥`    | Unresolved, malformed, unavailable, contradictory, or unverifiable required state |

Paper 2 defines the formal interface:

```
Admit₀(AR, G, Σ) → AD
```

***

#### Execution Intent

Current cross-paper public notation commonly uses:

```
E
```

for a concrete execution intent or AI-triggered action under evaluation.

The exact tuple differs by research paper and domain.

For example:

```
E
=
general execution intent
```

while:

```
E_FIN
=
financial execution intent
```

in LPP-FIN.

***

#### Human Intent

GitBook v2.0 uses:

```
H
```

when referring to:

> **Human-Authorized Intent**

and:

```
B_H
```

for the authority–intent binding:

```
B_H = ⟨AO, H⟩
```

Published papers may also use `H(·)` as a hash function in local mathematical notation.

To avoid ambiguity in GitBook v2.0 prose, cryptographic hashing should preferably be written as:

```
Hash(x)
```

when the surrounding context could confuse it with Human Intent `H`.

***

#### Permit Symbol

Paper 2 uses:

```
EP
```

for **Execution Permit**.

However, later Control Plane / Execution Plane technical specifications use:

```
EP
=
Execution Plane
```

This creates a historical notation collision.

GitBook v2.0 resolves it as follows:

```
CP
=
Control Plane
```

```
EP
=
Execution Plane
```

while Execution Permit should be written as:

```
Permit
```

or, in formal cross-paper notation:

```
π
```

where appropriate.

Thus:

```
PermitMinted(π, E, AO, G)
```

is preferred in cross-document explanatory material.

Published Paper 2 retains its original `EP` notation.

***

#### Evidence Symbols

```
AA
=
Admission Artifact
```

is used in current technical material.

Other evidence-object notation may be paper- or implementation-specific.

***

#### Financial Symbols

LPP-FIN uses:

```
E_FIN
=
Financial Execution Intent
```

```
G_FIN
=
Financial Governance State
```

and:

```
Admit_FIN(E_FIN, G_FIN)
```

for the financial-domain admissibility function.

Financial consequence classes are:

```
F0–F4
```

and map to the general LPP:

```
T0–T4
```

model.

***

#### Consequence and Risk Class Symbols

```
T0–T4
=
LPP General Consequence & Irreversibility Classes
```

```
F0–F4
=
LPP-FIN Financial-Domain Classes
```

```
AM-R0–AM-R3
=
ActuMind Operational Risk Signals
```

The canonical rule is:

```
AM-R
≠
LPP T-class
```

***

#### Symbol Precedence Rule

If a published paper uses a symbol differently from GitBook v2.0:

> **The paper's own symbol table governs interpretation of that paper.**

GitBook v2.0 notation governs the cross-document public architecture.

This prevents later terminology normalization from changing the historical mathematical meaning of already published research.