01
Changes and explanations
Show commits and their component staged items, including the messages attached to individual pieces of work.
Kovheim / Work in progress
A home for repositories, not a copy of GitHub.
Kovheim is intended to present Kov repositories on the web in a way that follows Kov’s own model: files, branches, commits, explanations, diffs and file operations shown as understandable project history.
WIPRead-only viewer firstKov-native
First milestone
Read the repository before trying to host it.
The first useful version of Kovheim does not need accounts, collaboration or remote transport. It needs to read a Kov repository correctly and present what is already there.
That creates a clean architecture: repository reader → standard repository model → API → website.
kov / main
src/Move CLI parsing into command layer2h ago
tests/Add reverse operation coverage1d ago
README.mdClarify staged-state behaviour2d ago
pyproject.tomlProject metadata5d ago
What it should understand
Repository history as structured meaning.
Kovheim should display the things Kov records directly rather than flattening them into generic diffs.
02
File operations
Present renames, moves, copies and deletions as first-class events, preserving their actual meaning.
03
Repository shape
Browse files, branches, merges, symlinks, executables and diffs through a Kov-native repository model.
Road forward
Build the foundation in layers.
Phase 01
Local read-only viewer
Read an existing Kov repository and render its history and files faithfully.
Phase 02
Stable repository API
Separate repository parsing from presentation so other tools can use the same model.
Phase 03
Hosted repositories
Add networked storage and remote workflows only after the local model is dependable.
Later
Collaboration
Accounts, permissions and shared workflows can grow around a model already proven by real Kov usage.