Roadmap Boundaries
Implemented Today
Section titled “Implemented Today”- single-region primary/replica key/value database with automatic leader election
- framed binary transport
- optional TLS and mTLS
- authentication enabled by default with an explicit local/trusted disable flag
- encrypted snapshot + WAL durability
- WAL-based replication with snapshot bootstrap and quorum-backed write acknowledgement by default
- audit log
- zstd frame compression enabled by default with an explicit disable flag
- atomic single-node
EXEC - server-managed storage keyring
- RustSec dependency audit in CI
Not Implemented Today
Section titled “Not Implemented Today”- sharding
- distributed transactions
- MVCC
- formal isolation levels
- multi-user ACLs
- online backup/restore tooling
- TLS certificate automation or rotation
Why This Matters
Section titled “Why This Matters”Vaylix is being shaped for those future capabilities, but the codebase should not pretend they already exist.
The documentation should follow the same rule:
- document shipped behavior as shipped behavior
- document roadmap constraints as roadmap constraints
- avoid vague marketing language that hides technical gaps
- do not describe opt-in controls as mandatory controls
That honesty is useful to contributors, operators, and anyone evaluating the project.