The Identity Model describes what an identity is inside LIVRE OS, independently of any UI or storage implementation.

At a high level, an Identity consists of:

• one or more keys
• a set of attributes (facts)
• a set of policies
• a commitment that binds them all together
• a lifecycle (created, active, rotated, recovered, retired)

Core Objects

Identity

Identity {
  identity_id        // stable internal identifier (UUID / hash)
  livre_name?        // optional LivreID: e.g. odin.livre
  current_commitment // hash binding current state
  state              // created | active | recovery | retired
}

LIVRE OS defines identity as:

A cryptographic commitment controlled by a user, enriched with claims, governed by policies, and provable without revealing personal data.

A LIVRE Identity is not a profile, account, or wallet.

It is a cryptographic object that:

• binds together keys, attributes, and policies
• can generate proofs about itself
• can evolve over time without losing continuity
• never exposes raw personal data outside the Livre Vault.

At the center of the model are three main trees maintained inside the Vault:

1. Key Tree
   • Control keys (day-to-day usage)
   • Recovery keys (long-term, rarely touched)
   • Device keys (optional, per device)
   • Rotation metadata