57cf2f7 ←9cf6fb4antonApr 5, 2026 api

edit hierarchical.md via macOS (conflict)

M /docs/undefined +0 -1
✎ modified paragraph change docs/markdown/syntax.md:
✎ modified code block docs/markdown/syntax.md ← file changed docs/markdown/ ...
✎ modified code block git clone https://sublimated.com/docs.git # who...
✎ modified list item gists — a single file in a folder is a gist with version his...
✎ modified list item dotfiles — clone on any machine, push changes, version histo...
✎ modified list item scoped access — each team clones only the folders they need
✎ modified list item agent workspace — an AI agent clones a folder, works in it, ...
✎ modified code block sublimated.com/docs/markdown → shows commits that touched ...
M /docs/undefined +0 -1
4 unmodified lines
5## how it works
6
7a space is a tree. when you change a file, sublimated creates commits at every level of the tree.
8
9change `anton/blog/archive/post.md`:
9change `docs/markdown/syntax.md`:
10
11```
12anton/blog/archive/post.md ← file changed
13anton/blog/archive/ ← commit created here
14anton/blog/ ← commit created here
15anton/ ← commit created here (space root)
12docs/markdown/syntax.md ← file changed
13docs/markdown/ ← commit created here
14docs/ ← commit created here (space root)
15```
16
17all commits are created in one atomic transaction. each level's commit contains a tree rooted at that level — only the files under that folder.
18
1 unmodified line
20
21because real commits exist at every level, you can clone any folder independently:
22
23```bash
25git clone https://sublimated.com/anton.git # whole space
26git clone https://sublimated.com/anton/blog.git # just blog + children
27git clone https://sublimated.com/anton/blog/archive.git # just archive
24git clone https://sublimated.com/docs.git # whole space
25git clone https://sublimated.com/docs/git.git # just git docs
26git clone https://sublimated.com/docs/markdown.git # just markdown docs
27```
28
29each clone gets:
30- only files under that path
6 unmodified lines
37## what this enables
38
39the hierarchical model gives you several things without needing separate products:
40
42- **gists** — a single file in a folder is a gist with version history. `sublimated.com/anton/snippets/hello.py`
43- **dotfiles** — `sublimated.com/anton/dotfiles/` — clone on any machine, push changes
41- **gists** — a single file in a folder is a gist with version history
42- **dotfiles** — clone on any machine, push changes, version history
43- **personal storage** — private space with file history, clone and sync anywhere
45- **scoped access** — clone only `platform/api/` or `platform/frontend/`, each team gets just what they need
44- **scoped access** — each team clones only the folders they need
45- **dataset versioning** — every change tracked, any version reproducible, clone a subset for experiments
47- **agent workspace** — an AI agent clones a folder, works in it, pushes results. full history of what the agent did
46- **agent workspace** — an AI agent clones a folder, works in it, pushes results with full history
47
48## version history per folder
49
51browse 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.
50browse 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.
51
52```
54sublimated.com/anton/blog/archive → shows commits that touched archive/
55sublimated.com/anton/blog → shows commits that touched blog/ (including archive/)
56sublimated.com/anton → shows all commits in the space
53sublimated.com/docs/markdown → shows commits that touched markdown/
54sublimated.com/docs/git → shows commits that touched git/
55sublimated.com/docs → shows all commits in the space
56```
57
58same for `git log` after cloning — you only see relevant history.
59
14 unmodified lines