Now
Complete persistent local namespace state and full operation application.
Backlog
Prioritized by what unlocks the next milestone.
The backlog is grouped by execution order, not just by subsystem. The immediate focus is finishing the real local state machine, then carrying that same logic into replication and user-facing surfaces.
Next
Bring up real replication and the first production-meaningful facade.
Later
Add encryption, proofs, energy-aware behavior, and operator tooling.
Research
Keep ZK, privacy, and advanced systems work feature-gated until the baseline is solid.
Highest-priority backlog
- Replace placeholder apply logic with real CRDT-backed state transitions
- Persist actual inode and directory mappings
- Build snapshots from live namespace state
- Expand admin visibility into local storage and applied state
Next unlocks
- Implement oplog synchronization between peers
- Add blob transfer and verified remote apply
- Choose and ship the first real external facade
- Integrate encryption and transparent proof enforcement
Planning
Roadmap and backlog now work together
The roadmap defines milestone outcomes. The backlog defines the concrete queue that moves the project toward those outcomes.