# Dapp Overview

The Overra Dashboard provides the operational interface for interacting with the local agent.

**It allows users to:**

* Monitor system state
* Initiate authorized containment
* Manage wallet authority
* Review audit logs
* View registered devices

The dashboard does not enforce containment directly. All state mutation occurs within the local agent after successful cryptographic verification.

***

### Design Philosophy

The dashboard is designed with a "State First" approach.

System state is always visible before controls.

This ensures operational clarity and reduces accidental actions.

The interface reflects security posture rather than offering broad administrative functionality.

***

## 1. Overview Page

The Overview page displays the current system status.

#### System Status Banner

**A large state indicator clearly shows:**

* **🟢 SYSTEM STATUS: NORMAL**
* **🔴 SYSTEM STATUS: CONTAINED**

This is the primary operational signal.

#### System Metadata

**Displayed information includes:**

* Registered Wallet (truncated)
* Device ID
* Agent Version
* Last Authorization Timestamp
* System Integrity Status

The goal is transparency. Users should immediately understand the system’s posture.

***

## 2. Containment Page

This is the primary action page.

#### Containment Toggle

**The interface presents a clear control:**

* ENTER CONTAINMENT MODE
* RELEASE CONTAINMENT

All actions require wallet signature verification. Containment cannot be triggered without cryptographic authorization.

#### Predefined Configuration

Containment actions are visible but not dynamically editable.

**Examples include:**

* Disable Network Interfaces
* Revoke Active Sessions
* Freeze Critical Applications
* Lock System

The system does not allow arbitrary rule creation.

***

## 3. Authority Page

The Authority page displays wallet binding information.

#### Registered Authority

**Shows:**

* Wallet address
* Date registered
* Last verification timestamp

#### Authority Update

Users may request authority update.

This requires valid signature from the current authority.

No backend override exists.

Authority changes are cryptographically enforced.

***

## 4. Audit Logs Page

The Audit Logs page provides structured event history.

**Each entry includes:**

* Timestamp
* Event type
* Result status
* Device identifier
* Reference hash (where applicable)

**Users can filter by:**

* Authorization events
* Verification failures
* State transitions
* System errors

Audit logs are append-only. Entries cannot be modified through the dashboard.

***

## 5. Devices Page

The Devices page is designed for future scalability. Even if operating in single-device mode, the UI supports multi-device architecture.

**Displayed information includes:**

* Device Name
* Current Status
* Last Heartbeat
* Integrity Check Status

Device-level detail pages may provide additional state visibility.

***

### Trust Boundary Reminder

The dashboard is an interface layer.

**It does not:**

* Verify signatures
* Execute containment
* Mutate system state independently

All critical security operations occur inside the local agent. The dashboard exists for visibility and interaction not enforcement.

***

### Operational Summary

**The dashboard enables:**

* Transparent state monitoring
* Controlled containment requests
* Authority management
* Structured audit review

It reflects the system’s deterministic design while maintaining clear separation between interface and enforcement layers.


---

# 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/usage/dapp-overview.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.