Operations

Built for practical deployment, even early.

NexusFS is meant to be operable as a single local process first, then expanded into a networked system with stronger replication, security, and scheduling policies over time.

Configuration

TOML config covers node identity, storage paths, admin binding, peers, optional facades, security mode, and energy thresholds.

Runtime State

Local data includes the storage backend, generated identities, head metadata, and the foundation for future peer state.

Admin Visibility

The embedded admin layer is the local control plane for status, storage, oplog inspection, and future replication telemetry.

Evolution Path

The codebase is staged to keep every milestone runnable while new transport, proof, and facade features arrive incrementally.

Suggested workflow

Use the example config for local development.
Run focused crate tests during implementation.
Validate the workspace before pushing milestone changes.
Keep public docs and deep specs aligned as behavior changes.