KOV
The keeper
Represented in aged bronze with books and runes: the part of the project concerned with preserving and understanding history.
About
Built by learning, testing and rebuilding.
Kovheim is a long-term software project centred on making technical systems easier to understand without making them shallow. Kov is the first foundation; Taosen and Kovheim grow around it.
Why it exists
Complexity should earn its place.
Version control is powerful, but many developers learn its behaviour as a collection of commands before they develop a clear mental model of what the system is actually doing.
Kov is an attempt to explore a different starting point: explicit intent, understandable state and recovery mechanisms that are visible rather than magical.
Kovheim extends the same idea to the web. Instead of treating repository hosting as the product and version control as a back end, it starts with the repository model and asks how the web can make that model easier to inspect.
The names
Three roles in one system.
The project identities are represented as three mythological figures: a keeper, a teacher and a guardian.
TAOSEN
The teacher
Represented in pale marble with an open book: the learning layer, intended to make programming concepts understandable through practice.
KOVHEIM
The guardian
Represented as a dark guardian sheltering a lit home: the place where the work can eventually live, be viewed and be shared.
Development philosophy
Use the tools, find the friction, then let the real problems shape the product.
Build for real use
Kov is meant to be used during development so design weaknesses appear through actual work.
Keep the model visible
The system should make important state understandable rather than hiding it behind convenience.
Learn through construction
The surrounding projects are also a way to learn software design by building increasingly capable systems.