Reliability

Durability before mutation.

TriviumDB's write path is designed around recovery. Mutations are validated, recorded in a CRC-protected write-ahead log, flushed across fsync boundaries, checkpointed with atomic rename, and replayed on startup when needed.

1. Dry runValidate the combined vector, payload, and edge operation before committing it.
2. WAL + CRCAppend checksummed frames so recovery can detect unsafe or torn tails.
3. fsync + renameFlush durable bytes and publish checkpoints atomically.
4. ReplayOn startup, complete safe records and preserve a consistent node space.