Roadmap

The path from demo node to sovereign network.

We start with a single Identity Node, then grow into a networked identity fabric: Solivre Kernel, LivreID naming, hardened Vault, and app-facing Verifier flows.

Timelines are indicative, not promises. This page is a living map of what we’re actively forging.

Done Forging now On deck
M1 · Identity Node MVP Done

Define MVP scope & ship the first Identity Node.

Basic Identity Node with Agent + Verifier consoles, file-based Vault, and deterministic age/residency proof templates wired into a simple proof engine.

Identity Node v0.x Agent / Verifier File-based Vault
M2 · Solivre Kernel & Vault spec Forging

Stabilize the Solivre Kernel & harden the Vault model.

Extract a minimal Solivre Kernel interface from the node, define how claims, policies, and proof descriptors are represented, and draft a hardened Vault spec with pluggable backends and rotation.

Kernel API draft Claims & policies Vault design
M3 · LivreID namespace On deck

Launch the LivreID naming layer for identities.

Specify how odin.livre and similar names resolve to private identity anchors, not public profiles. Design registration, renewal, and privacy guarantees so apps see anchors, never documents.

.livre names Resolution rules Privacy model
M4 · Proof flows & on-chain orchestrator Planned

Move from manual JSON copy/paste to real proof request flows.

Define a standard “Proof Request” schema, build request/response flows between apps, Agents, and Identity Nodes, and experiment with an on-chain orchestrator on COTI gcEVM for anchoring proof hashes and policies.

Proof Request schema Verifier UX On-chain anchors

Everything above is intentionally small and composable. LIVRE OS grows by hardening each layer — Kernel, Vault, LivreID, Wallet — not by shipping a monolith in one go.