Identity creation
Create multiple local identities and switch between them via a simple dropdown.
Solivre MVP Suite
Watch the identity layer come alive.
A small constellation of prototypes — Identity Node, Agent, Verifier, Vault, Kernel — proving that apps can ask for signals, not your soul.
Running locally, evolving steadily. Some pieces are live, others are still being forged.
Identity Node
One node that keeps your Vault, serves your consoles, and orchestrates proofs.
- Stores identity records, attributes, and commitments in an encrypted Vault.
- Generates deterministic demo proofs for age + residency templates.
- Hosts Agent & Verifier on the same origin for frictionless demos.
Agent Console
The human-facing shell for creating identities, attaching attributes, and exporting proofs.
Attributes & Vault
Bind birthdate + country to identities and persist them in an encrypted Vault file.
Proof export
Generate age/residency proofs and export the Identity + Proof bundle as JSON.
This console will grow into a full Solivre Agent: multiple proof templates, app-specific request flows, and notifications when new proof requests arrive.
Verifier Console
A clean surface where integrators can see exactly what a proof says — and what it doesn’t.
- Paste the Identity JSON exported from the Agent.
- Paste the Proof JSON (or the combined bundle).
- Click Verify to check the proof against stored attributes + the template logic.
Livre Vault
Encrypted storage that will back the Identity Node and later the full LIVRE OS network.
The current MVP uses a simple file-based Vault for development only. A hardened Vault spec — pluggable backends, rotation, multi-device sync — is being refined and tested. Working on it
ID Kernel
The minimal API surface other apps call to resolve identities, claims, and proofs.
The ID Kernel spec exists in draft form and will be implemented once the Solivre demo flows stabilize. It’s the piece that lets any app say: “ask Solivre, not my database.” Growing soon