Preserve context
Confirmed goals, decisions, project knowledge and unresolved questions remain attached to the project instead of disappearing with one chat or provider session.
Between the coding agent and durable project state
Livariant combines durable project context, explicit authority, evidence-based verification and recovery into one controlled operating model for AI-assisted development.
The product model
Livariant is neither an IDE nor an AI model. It defines the rules by which agent work may become durable project state.
Confirmed goals, decisions, project knowledge and unresolved questions remain attached to the project instead of disappearing with one chat or provider session.
Livariant reconstructs the existing project state before new knowledge is promoted into durable project context.
Technical capability is not permission. Observation, proposal, authorization and mutation remain distinct.
Requirements, claims and evidence are evaluated separately so that results can be supported, contradicted or left explicitly unproven.
Provider-facing context is prepared locally and remains associated with project identity and provenance. Provider capabilities are not treated as identical: Codex, Claude Code, Gemini CLI and Custom providers expose different levels of session evidence, retrospective attribution and diagnostics.
Where a supported recovery strategy and valid checkpoint exist, consequential changes can be brought back into a known state without weakening authority boundaries.
Scope
Contains the current integrated product state and is the canonical target for normal development work.
The currently published Preview has its own immutable source identity and a narrower independently qualified release scope.
Next