# Overra Model

Overra introduces a deterministic containment model for Web3 endpoints.At its core, Overra binds cryptographic wallet authority to device-level state enforcement. It does not expand control. It formalizes containment as a verifiable state transition.

***

### Core Principle

In Web3, authority is cryptographic.

If ownership and governance are enforced through signatures, endpoint containment should follow the same principle.

**Overra establishes a simple but structural model:**

`Wallet → Signed Authorization → Local Verification → Deterministic State Transition`

Containment becomes a cryptographically authorized event.

***

### Authority Model

Each endpoint registers a single wallet as its root authority.

**Only this wallet may authorize:**

* Transition into containment
* Release from containment
* Authority updates

Authorization is structured, signed, and verified locally.

No centralized credential system exists.

No administrative override exists.

Authority derives exclusively from cryptographic proof.

***

### Deterministic State Machine

**Overra operates under a finite state model:**

* **NORMAL**
* **CONTAINED**

State transitions occur only after successful verification.

Invalid or replayed requests do not mutate state.

There are no partial containment states.

There are no hidden transitions.

This ensures predictability and auditability.

***

### Local Verification

All verification occurs inside the local Rust agent.

**The agent validates:**

* Ed25519 signature authenticity
* Authority match
* Nonce uniqueness
* Timestamp integrity
* Expiration window compliance

Only after verification succeeds does containment execute. Enforcement does not depend on centralized services.

***

### Constrained Containment

Containment actions are predefined and intentionally limited.

**They may include:**

* Network interface restriction
* Session revocation
* Application freeze
* System lock

**The system deliberately excludes:**

* Remote shell access
* Arbitrary command execution
* Dynamic scripting
* Surveillance features

Constraint reduces attack surface.

***

### Auditability

Every authorization attempt and state transition is recorded in append-only logs.

**This ensures:**

* Traceability
* Transparency
* Post-incident analysis capability

Security without auditability is incomplete.

***

### A Structural Layer

Overra is not a monitoring dashboard.

It is not a centralized IT tool.

It is a containment primitive for the Web3 execution layer.

By formalizing wallet-authorized, locally enforced containment, Overra closes the structural gap between cryptographic ownership and endpoint state control.

It transforms containment from discretionary action into infrastructure.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://overra.gitbook.io/overra-docs/overra-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.