Console Overview
The server-blind entry point to your agent memory ecosystem.
| Deployment Model | Availability |
|---|---|
| Platform | ✓ Available |
| Self-Hosted | ✓ Available |
Honesty Ledger (Provenance Layer): This interface displays metrics aggregated from both Server-known (Layer A) and Client-derived (Layer B) components.
ZK Trust Boundary:
- What the server sees: Coarse connection metadata, total encrypted envelope count, and AES ciphertext bytes.
- What stays on device: All plaintext memory text, vector index queries, and search histories.
The Server-Blind Console
The sovseal console is designed from the threat model up to ensure that you never have to choose between rich operational visibility and absolute data privacy. Under standard cloud dashboards, developers look at raw data tables and cleartext query logs. Under sovseal, the server running the dashboard is completely blind to your content.
Tenant & Project Switcher
In the upper-left corner of the workspace, you can switch between organizations and projects:
- Project Isolation: Switching projects re-scopes all Layer-A requests and charts.
- Key Partitioning: Switching projects prompts the client browser to load the encryption key specific to that project. There is strictly zero cross-project content bleed.
Console Lifecycle States
Because decryption keys are held strictly in-browser memory (and never persisted in storage or escrowed on servers), the console renders in three distinct lifecycle states based on key availability:
- Skeleton Loading (
MODE === "skeleton"): Pulsing placeholder components render when first establishing connection to the edge database, showing no numbers. - 🔒 Locked (Pre-Key Load): If the project key is not loaded in browser memory, Layer-A indicators (Sync Ops, Bytes Stored, Devices) are fully populated, but Layer-B explorer cards display a lock icon:
🔒 Load your key. This is a core trust demonstration—not a failure state. - Unlocked (Key Loaded): The browser imports your AES-256-GCM key. All Layer-B metrics (Memory count, topics, lineage explorer) unlock instantly via local decryption.
AI Support Assistant (Fin)
The floating chatbot assistant (Fin) in the bottom-right corner is configured strictly for product documentation Q&A:
- Zero Content Access: Fin does not run in the same context as the decrypted memory viewer.
- Key Isolation: The assistant process can never read your encryption key, your memory vectors, or your ciphertext.
Offline Reference Analogs: This documentation was written with visual and rhythm reference to platform/features/platform-overview.html.