Implemented now
Runnable daemon and CLI, sled-backed local persistence, canonical object hashing, chunked CAS writes, snapshots, and minimal admin APIs.
Current Status
Implemented foundations, not full end-to-end sync yet.
NexusFS is in an early but practical milestone: the local-core baseline is real, the workspace is runnable, and the public project surface is in place. Full replication, facades, and proof enforcement are still in the backlog.
In progress
Milestone M1 is underway with real local-core plumbing, but the full CRDT-backed filesystem apply path is not complete yet.
Present as scaffolding
QUIC, transparent proofs, S3, POSIX, privacy, energy, and ZK crates all exist, but most are still placeholders or partially wired layers.
Highest-value backlog
Finish the real local state machine, then move into oplog and blob replication between nodes.
Implemented now
- Single-binary workspace and runnable `nexusfs` commands
- Persistent config, device identity, and admin token flows
- Sled-backed blob and KV storage with tests
- Canonical object encoding, hashing, chunking, and snapshot heads
- Minimal idempotent oplog application and clock summaries
- Embedded admin API for status, head, and oplog summary
Still in backlog
- Full CRDT-backed directory and inode mutation logic
- Real peer replication and blob transfer
- Integrated encryption-at-rest write path
- Automatic proof attachment and verification enforcement
- Functional S3 and POSIX facades
- Energy-aware scheduling wired into background jobs
Source Of Truth
The markdown status file lives in the repo
The detailed implementation and backlog breakdown is maintained in the `documentation/current-status.md` file alongside the rest of the public-facing docs.