A Rust + gRPC sync engine designed to understand git, branches, and platform-specific binaries natively. It is designed to replace Syncthing and Dropbox for Obsidian vaults shared across macOS, Linux, and Windows machines. After a sync incident corrupted a Rust target/ folder during a build, the project codified a strict policy: never sync .git, .venv, node_modules, target — Disk Arcana is designed to enforce this by default.
- Status
- In active development
- Autonomy (AAL)
- L1 → L4
- Stack
- Rust + gRPC
- Source
- Open source
01
Understands git
Git-aware delta sync is designed to skip .git/ and respect .gitignore.
02
Cross-platform binaries
macOS .dylib, Linux .so and Windows .dll are designed to be filtered per platform.
03
Safe by default
Built-in ignore patterns are designed to cover 25+ artifact classes: cache dirs, lockfiles and build outputs.
The incident behind the policy
A sync incident corrupted a Rust target/ folder during a build. The project then codified a strict policy: never sync .git, .venv, node_modules, target.
Disk Arcana is designed to enforce this by default. It targets Obsidian vaults shared across macOS, Linux and Windows machines, and is designed to replace Syncthing and Dropbox.
Capabilities
Planned
- Git-aware delta sync (skips .git/, respects .gitignore)
- Conflict resolution via Claude CLI on three-way merges
Status not stated
- Cross-platform binary filtering (macOS .dylib / Linux .so / Windows .dll)
- Obsidian plugin for live sync without leaving the editor
- gRPC API + native CLI client
- Pre-flight inventory checklist for new sync setups
- Built-in ignore patterns for 25+ artifact classes (cache dirs, lockfiles, build outputs)
Current autonomy level
Weakest link
In active development — runtime not yet hardened. The earlier sync incident showed how easy it is to corrupt a Rust target/ folder when sync products fight over file locks; Disk Arcana must demonstrate it does not repeat that failure mode.
Roadmap to L4
- L2 lift — health endpoint, structured pino-equivalent logs, deploy reporting to Ops Bot.
- L3 → L4 — fallback to rsync for incompatible filesystems, audit log of every sync action, conflict-storm circuit breaker, recovery checkpoint per device.
- Verification gate — three-machine soak test (macOS / Linux / Windows) for 30 days without manual conflict resolution.
Links
Next step
Review the current build and its development plan
BUILDING means active development, not a promise of public availability. Use the current capabilities and roadmap above as the reference.
Review the path to the target level