> 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/7.-mind-universe-governance-stack/7.8-residentmode.md).

# 7.8 ResidentMode

**ResidentMode** is the runtime defense system within the Jarvis governance architecture.

Its purpose is to respond when the task-governance process detects anomalies, semantic pressure, structural inconsistency, or attempted governance bypass during operation.

The historical Jarvis reference architecture places:

```
ResidentMode
SilentOverride
ResidentTrigger
```

inside the Runtime Defense Layer.

#### ResidentTrigger

ResidentTrigger activates runtime defense when defined anomalies appear.

Reference trigger conditions include:

* semantic drift,
* task escalation,
* responsibility ambiguity,
* TaskChain errors,
* or related governance anomalies.

Conceptually:

```
Governance Anomaly
        ↓
ResidentTrigger
        ↓
ResidentMode
```

#### ResidentMode Functions

The reference subsystem includes functions such as:

* Error Chain monitoring,
* semantic-pressure evaluation,
* sentence cooling,
* breach detection,
* cross-module slip control,
* and task locking.

Reference outcomes include:

```
Lock
Warning
Cooldown
```

#### Runtime Containment

ResidentMode exists because semantic and task governance cannot assume that a task remains stable after initial intake.

An anomaly may emerge during:

* task evolution,
* module routing,
* repair,
* multi-step processing,
* or preparation of an Action Candidate.

ResidentMode provides a containment path.

#### SilentOverride

SilentOverride is defined in the Jarvis technical lineage as a mechanism preventing:

* statements that bypass semantic pre-check,
* or invalid module invocation.

It is therefore an internal anti-bypass mechanism within Jarvis runtime governance.

#### ResidentMode Is Not LPP Revocation

The distinction must remain clear.

ResidentMode may lock or contain a task because the Jarvis runtime has detected an anomaly.

LPP revocation concerns whether legitimate authority itself remains active.

Therefore:

```
ResidentMode Lock
≠
Authority Revocation
```

Likewise:

```
ResidentMode Clear
⇏
LPP ADMIT
```

Runtime defense and constitutional admissibility remain separate governance responsibilities.