Architecture

One binary, layered responsibilities.

The architecture keeps local state deterministic and verifiable while leaving plenty of room for replication, optional facades, and future proof systems.

Core invariants

  • Objects must be encoded canonically before hashing.
  • Content-addressed objects are immutable.
  • Filesystem mutations are signed operations.
  • Replication must be safe to replay.
  • Remote state is accepted only after verification.
Layered NexusFS architecture diagram.

Core + Storage

Chunking, object modeling, snapshots, CAS, and KV persistence.

Protocol + CRDT

Stable operation types, causal context, and deterministic merge rules.

Crypto + Proofs

Signing, at-rest encryption, transparent proofs, and future ZK layers.

Transport + Facades

QUIC replication, admin UI, S3-like APIs, and future POSIX mounting.