LIVARIANTGitHubexternal
ProductLocal control layerProvider-aware architecture

Between the coding agent and durable project state

A clear boundary between a proposal and project truth.

Livariant combines durable project context, explicit authority, evidence-based verification and recovery into one controlled operating model for AI-assisted development.

Agent observes and proposesLivariant controls the transitionProject state remains traceable
AI OUTPUT / UNTRUSTEDPROJECT TRUTH / DURABLE
Observationnot project truth yetContextprovenance stays visibleAuthorityexplicit decisionVerificationevidence-backed state
01

The product model

Six capabilities. One continuous control model.

Livariant is neither an IDE nor an AI model. It defines the rules by which agent work may become durable project state.

01Project Brain

Preserve context

Confirmed goals, decisions, project knowledge and unresolved questions remain attached to the project instead of disappearing with one chat or provider session.

02Project Understanding

Understand first

Livariant reconstructs the existing project state before new knowledge is promoted into durable project context.

03Authority

Bound consequential actions

Technical capability is not permission. Observation, proposal, authorization and mutation remain distinct.

04Verification Trace

Verify outcomes

Requirements, claims and evidence are evaluated separately so that results can be supported, contradicted or left explicitly unproven.

05Provider Handoff

Move between providers

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.

06Recovery

Plan for failure

Where a supported recovery strategy and valid checkpoint exist, consequential changes can be brought back into a known state without weakening authority boundaries.

02

Scope

Current development model

Repository develop

Contains the current integrated product state and is the canonical target for normal development work.

Separately qualified

Desktop Preview rc.29

The currently published Preview has its own immutable source identity and a narrower independently qualified release scope.

Next

Understand where data stays local — and where it can leave your machine.