Honesty Ledger (Provenance Layer): This page tracks parameters and connections managed at the Server-known (Layer A) layer. ZK Trust Boundary:
- What the server sees: Sync connection handshakes, agent identifier hashes, and network packet sizes.
- What stays on device: Cleartext local data, configuration files, and raw encryption key secrets.
Onboarding and Integration
To enable agent memory storage and retrieval, you must connect a sync source. The console provides copy-paste integration snippets tailored to your deployment architecture.- MCP Server (Zero-Config)
- MCP Server (Cloud Sync)
- Node SDK
- Self-Hosted Edge
Key Configuration Parameters
SOVSEAL_API_KEY: Your paid tier API Key (starting withsov_live_) obtained from the console dashboard. If running local-first, the client handles project identity (sov_proj_) silently under the hood.SOVSEAL_ENCRYPTION_KEY: A cryptographically secure 256-bit (64-hex) key generated locally on your machine. This key never leaves the host machine and is never sent to the network.
Agent sync check
On the right side of the onboarding pane you will see the Onboarding Progress stepper:- Load Identity Key: Generates or loads the local key material from your OS keychain.
- Copy Integration Snippet: Confirms the configuration snippet was copied.
- First Memory Synced: The dashboard polls for the first AES-256-GCM encrypted envelope to arrive at the replication endpoint. When a real sync lands, the stepper advances automatically.
This step waits for a real sync from your agent — there is no simulate button. If the stepper does not advance, your client has not yet replicated an envelope; check that the MCP server or SDK is running and that
SOVSEAL_API_KEY is set for cloud sync.