01 / KOV
The keeper of history.
A local-first version control system focused on explicit staging, understandable changes, recovery and experimentation.
Work in progress
A home for deliberate software
History should help you move forward.
Kovheim is the home of Kov: a version control system being built around understandable history, deliberate actions, safe recovery, and the freedom to experiment without losing sight of what changed.
KOV
TAOSEN
KOVHEIM
The ecosystem
Three ideas. One direction.
Kov, Taosen and Kovheim serve different roles, but share the same aim: software that is understandable enough to learn from and dependable enough to trust.
02 / TAOSEN
The path of learning.
A teaching and learning project intended to make programming concepts understandable through building, not abstraction alone.
Planned
03 / KOVHEIM
The home of the work.
A future home for Kov repositories: readable project history, files, changes and context without simply copying the shape of existing forge platforms.
Work in progress
Principle
Your work is safe, its history is understandable, and every experiment is reversible.
Built around the person doing the work
Kov starts with the individual developer. The design does not assume that every workflow must look like Git, or that power has to come with opaque terminology and hidden state.
The aim is to make each action legible: what is staged, what changed afterwards, what will be committed, and how to reverse something without rewriting history.