kin-vfs
v0.1.0ActiveApache-2.0Transparent file projection for the semantic substrate
kin-vfs is the virtual filesystem layer that makes graph-backed semantic state look like a normal working tree to any tool that expects files. It replaces the old editor-fork narrative with a reusable projection layer: keep the graph authoritative, project files only where needed.
Current public tag
v0.1.0
Sourced from the current public GitHub tag.
Primary purpose
Projection
Serve normal file reads above the semantic substrate.
Narrative impact
No forks
Editor-native behavior without turning the editor itself into the product boundary.
Why It Matters
The current Kin architecture no longer needs a dedicated editor fork to feel graph-native. kin-vfs is the compatibility layer that lets normal file-based tools sit above semantic truth.
Transparent reads
Tools open what looks like a normal file tree while kin-vfs serves content directly from the blob store.
No editor fork
The projection layer is generic. Any editor or CLI tool can sit above it instead of requiring a custom IDE fork.
Low-duplication working trees
Files are backed by content-addressed storage, which keeps checkouts lightweight and makes projections cheap.
Mac + Linux focus
Current primary targets are macOS via DYLD and Linux via LD_PRELOAD, with Windows ProjFS planned.
How It Fits
Below
KinDB and the Kin blob store keep the semantic and content-addressed state.
Middle
kin-vfs intercepts reads and serves projected files into normal tool workflows.
Above
Kin Editor, build tools, shells, and any file-oriented surface can operate without owning the truth model.