Core + Storage
Chunking, object modeling, snapshots, CAS, and KV persistence.
Architecture
One binary, layered responsibilities.
The architecture keeps local state deterministic and verifiable while replication, the facades and the commitment layer sit on top of it without reaching past it. Every one of them goes through the same signed-operation pipeline; there is no back door into the state machine.
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.
- Content is stored only when it was asked for.
- Durability sits at the operation boundary, not the record boundary.
Protocol + CRDT
Stable operation types, causal context, and deterministic merge rules.
Crypto + Proofs
Signing, at-rest encryption, transparent proofs, and a Merkle state commitment with inclusion and absence proofs. Not a proving system.
Transport + Facades
QUIC replication, the admin console, and an S3-compatible API. A POSIX mount is new scope rather than an unfinished one.