Roadmap
Ketebe’s roadmap prioritizes release evidence over feature accumulation. The core product surface is already broad; the next milestones prove that it can be packaged, recovered, upgraded, measured and operated predictably.
v0.9 — packaged release readiness
Publish a repeatable runtime image with versioned release semantics.
Make create → write → query possible from a standalone persistent deployment.
Versioned container publishing plus binaries and SHA verification assets.
Prove the packaged distribution survives the basic operational lifecycle.
Toward v1.0 — prove production behavior
The v1.0 path is intentionally evidence-heavy. The goal is not to add a long list of features just to change the version number.
- Longer-running soak and stability tests.
- Recovery and upgrade drills with repeatable procedures.
- Benchmark profiles that can be reproduced outside the development environment.
- Compatibility and migration verification across supported interfaces.
- Feedback from external users running real workloads.
Engineering principles
Fast behavior that cannot be recovered or explained is not a production win.
Clients should not need to know whether Ketebe is standalone or distributed.
Durable state is explicit; derived indexes are rebuildable state.
Scale, latency and throughput claims require repeatable evidence.