hierarchical versioning

this is what makes sublimated different from GitHub, GitLab, or any other git host. every folder in your space has its own independent git history, and changes cascade commits from the file level up to the root.

how it works

a space is a tree. when you change a file, sublimated creates commits at every level of the tree.

change anton/blog/archive/post.md:

anton/blog/archive/post.md   ← file changed
anton/blog/archive/           ← commit created here
anton/blog/                   ← commit created here
anton/                        ← commit created here (space root)

all commits are created in one atomic transaction. each level's commit contains a tree rooted at that level — only the files under that folder.

clone any folder

because real commits exist at every level, you can clone any folder independently:

git clone https://sublimated.com/anton.git              # whole space
git clone https://sublimated.com/anton/blog.git          # just blog + children
git clone https://sublimated.com/anton/blog/archive.git  # just archive

each clone gets:

• only files under that path

• only commits that touched that subtree

• branches scoped to that level

• a clean, self-contained git history

no sparse-checkout, no filtering. the server gives you a real git repo for that folder.

what this enables

the hierarchical model gives you several things without needing separate products:

• gists — a single file in a folder is a gist with version history. sublimated.com/anton/snippets/hello.py

• dotfiles — sublimated.com/anton/dotfiles/ — clone on any machine, push changes

• personal storage — private space with file history, clone and sync anywhere

• scoped access — clone only platform/api/ or platform/frontend/, each team gets just what they need

• dataset versioning — every change tracked, any version reproducible, clone a subset for experiments

• agent workspace — an AI agent clones a folder, works in it, pushes results. full history of what the agent did

version history per folder

browse to any folder on sublimated.com and you see its commit history — only the changes that affected that folder and its children. no noise from unrelated parts of the space.

sublimated.com/anton/blog/archive  →  shows commits that touched archive/
sublimated.com/anton/blog          →  shows commits that touched blog/ (including archive/)
sublimated.com/anton               →  shows all commits in the space

same for git log after cloning — you only see relevant history.

how it compares

on GitHub, a repo is the atomic unit. on sublimated, a folder is.

see git overview for how to clone and push, or branches for how branch scoping works with the hierarchy.