Your filesystem as an API. Endpoints are file paths; methods are the logical
operations Create, Read, Update, Execute, List, Delete;
all actual behavior lives in swappable controllers inside fsAPI/.fsAPI
directories. The core is deliberately dumb: it resolves, delegates, and pipes.
See Claude Code Initialization Prompt.md for the full architecture manifesto.
| dir | what | docs |
|---|---|---|
bus/ |
Rust shared-memory pipeline bus (fsapi-bus) |
bus/README.md |
core/ |
zsh root-command template (one per API) | core/README.md |
controllers/ |
default Router / Infer / MimeType controllers | controllers/README.md |
admin/ |
fsapi-admin global manager |
admin/README.md |
daemon/ |
crueld: the mapping daemon (all mapping logic lives here) | daemon/README.md |
(cd bus && cargo build --release)
export PATH="$PWD/bus/target/release:$PATH"
admin/fsapi-admin new ~/myapi --name api --yes
cd ~/myapi
print "hello" | ./api greeting.txt/create
./api greeting.txt/read # -> hello
./api greeting.txt # no method: the Infer controller asks you
./api -n greeting.txt/read # explain resolution without executingRoot commands map their own directory themselves — a flat API needs no daemon and no map. Nested fsAPI dirs deeper in the tree are the mapping daemon's job:
daemon/crueld enable ~/myapi # or: admin/fsapi-admin daemon enable ~/myapicrueld writes <root>/.fsAPI.map (nested dirs only, only into genuine API
roots) and keeps it live via inotify path units plus a sweep timer.
Phase 1 complete plus the crueld daemon: bus helper, root command template,
default controllers, admin tool, and crueld — each with its own test suite
(zsh <dir>/test.zsh, bus/smoke-test.zsh, cargo test).