Project status and limits
What exists, what has been tested and what remains before a usable database release.
Current status — 21 September 2026: prototype implementation is in progress. The registry marks P00–P23 and P25 done. P24 (full native acceptance) and P26 (mixed-load/resource qualification) are running. P27 (standalone package), P28 (complete operator and developer documentation), and P29 (final acceptance and handoff) are waiting. “Done” here means the packet is complete, not that the whole prototype is accepted or released. See the dependency contract.
Status: Development. This page separates completed implementation packets from work still being qualified and later acceptance gates. The version badge and changelog follow repository sources independently of this status.
Implementation and qualification
The completed packets cover the database engine, document and schema operations, queries and graphs, a local authenticated service, a first-party client, native interface work, backup and restore, branches and merges, analytics, and bounded Oracle/MCP views. Packet completion is not final product acceptance. There is no accepted local alpha, production release, downloadable database package or hosted service.
| Area | Evidence and boundary |
|---|---|
| Implemented packets | P00–P23 and P25 are marked done in the registry. This records packet completion, not acceptance of the full product. |
| Native acceptance | P24 is running; the complete native scenarios have not passed their final gate. |
| Mixed-load qualification | P26 is running; no benchmark or capacity result is claimed here. |
| Package and handoff | P27–P29 are waiting; there is no accepted release or downloadable package. |
Test results have a scope
Earlier test counts and build failures are dated historical checkpoints, not evidence for today's acceptance gates. Consult the current verification record for the scope of any executed check; do not combine results from different boundaries into a complete-suite claim.
What remains unavailable
The prototype has not passed its complete native, mixed-load, package, documentation or final acceptance gates. This status makes no claim of disk-scale warehouse capacity, clustering or federation.
There are no published RURAL throughput comparisons, hosting-cost guarantees, token-saving percentages, security certifications or independent power-loss certifications. Performance plans define what to measure; they are not results.
What makes the next milestone meaningful
The first useful alpha must let a real local application perform ordinary work against RURAL, retain acknowledged changes after the tested restart scenarios, restore a verified backup, use independent branches and ask grounded analytical questions. It must expose its limits and failure states through a usable interface.
Follow the roadmap for delivery gates and the changelog for recorded changes. A version number describes repository state; it is not a readiness certificate.