# Core Principles

Overra is intentionally minimal. Its design is shaped by a small set of architectural principles that prioritize determinism, constraint, and explicit trust boundaries. These principles guide all implementation decisions.

***

### 1. Infrastructure Over Tooling

Overra is designed as a structural layer, not a feature-rich security tool. It does not aim to monitor user behavior, analyze transactions, or provide broad administrative control.

**Its scope is narrow and deliberate:**

Deterministic containment of the execution environment. By remaining focused, Overra avoids expanding into areas that increase complexity and attack surface.

***

### 2. Authority Must Derive From Ownership

In Web3, authority is not granted through accounts or passwords. It is proven through cryptographic signatures. Overra preserves this model at the endpoint layer.

**No administrative accounts.**\
**No centralized credential systems.**\
**No override mechanisms.**

Authority is bound to wallet ownership. This ensures alignment with Web3-native trust assumptions.

***

### 3. Constraint as a Security Strategy

Security systems often fail when they become too powerful. Remote shells, dynamic scripting and unrestricted administrative controls introduce systemic risk. Overra intentionally excludes expansive functionality. Containment actions are predefined and non-extensible. Limiting capability reduces exploit surface and increases predictability.

***

### 4. Determinism Over Discretion

Containment is not discretionary. It is not subject to manual override once authorized. Overra enforces clear, predictable state transitions.

**Deterministic systems are auditable.**\
**Discretionary systems are ambiguous.**

Predictability strengthens security.

***

### 5. Explicit Trust Boundaries

**Overra separates:**

* Wallet (authority)
* Dashboard (interface)
* Agent (enforcement boundary)

The dashboard is not trusted to enforce state. Only the local agent may mutate containment state. Clear boundaries prevent privilege confusion.

***

### 6. Local-First Enforcement

Enforcement occurs locally. The system does not depend on centralized services for containment execution. This reduces dependency risk and preserves operational independence. Containment must function even under network uncertainty.

***

### 7. Transparency by Default

Every authorization attempt and state transition is logged.

Auditability is not optional.

Security infrastructure must be traceable and accountable.

***

### Principle Summary

**Overra is guided by:**

* [x] Minimal scope
* [x] Cryptographic authority
* [x] Deterministic behavior
* [x] Constrained capability
* [x] Explicit boundaries
* [x] Local enforcement

These principles ensure that Overra remains infrastructure not administrative software.


---

# 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/core-principles.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.