> 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/6.-intent-and-trajectory-governance/6.12-risk-indexed-quorum.md).

# 6.12 Risk-Indexed Quorum

The current trajectory-level model defines SVNN quorum requirements as dependent on risk or consequence rather than assuming one universal consensus threshold.

The research represents the applicable quorum configuration as:

```
G.Q[r]
```

where the required verification strength depends on the relevant risk level or governance profile.

#### Why Quorum Is Risk-Indexed

A low-consequence action and a sovereign or asset-critical action should not necessarily require identical verification strength.

The general rule is:

> **Quorum strength should not weaken as consequence increases.**

Higher-consequence profiles may therefore require stronger combinations of:

* minimum support,
* trust-domain heterogeneity,
* weighted threshold,
* mandatory validator roles,
* and veto conditions.

#### Minimum Support

A quorum may require a minimum number of supporting validators.

This prevents a high weighted score from being produced by an insufficiently small set of nodes where the applicable profile requires broader support.

#### Heterogeneous Trust Domains

Validators may be required to come from different trust domains.

This reduces the risk that apparent distributed consensus is actually one administrative or organizational authority represented several times.

Conceptually:

```
Multiple Nodes
≠
Multiple Independent Trust Domains
```

Heterogeneity may involve separation across:

* organizations,
* infrastructure domains,
* governance roles,
* jurisdictions,
* or other independent trust boundaries.

The exact production definition is profile-specific.

#### Weighted Threshold

Validators may carry different verification weights under the applicable governance profile.

A quorum may therefore consider both:

```
How many validators support?
```

and:

```
What qualifying weight do they represent?
```

#### Mandatory Roles

Some profiles may require evidence from specific validator roles rather than permitting any arbitrary collection of nodes to satisfy quorum.

This prevents a large number of low-authority or homogeneous validators from replacing a required specialist or independent verification role.

#### Veto

The model supports veto semantics where an applicable mandatory validator or governance condition can prevent quorum satisfaction.

This is consistent with the non-compensatory nature of LPP.

A large amount of favorable evidence must not necessarily cancel a mandatory disqualifying condition.

#### Public Reference Model

Conceptually, a risk-indexed quorum may require that:

```
Minimum support is satisfied
∧
Required trust-domain diversity is satisfied
∧
Weighted threshold is satisfied
∧
Mandatory roles are present
∧
No applicable veto blocks acceptance
```

The specific numerical thresholds, production weights, and operational escalation rules are not fixed by this public chapter.

Those values may be profile-specific or controlled technical material.

#### High-Consequence Fail-Closed Rule

Where a governance profile requires SVNN verification and the required quorum cannot be established, high-consequence execution must not treat missing consensus as positive evidence.

Thus:

```
Required Quorum Unresolved
≠
Semantic MATCH
```

and never:

```
Required Quorum Unresolved
→ automatic ADMIT
```

The final decision remains with the Admission Kernel.

***