Roadmap

Status: implementation in progress. This roadmap describes product acceptance gates, not a second task board. Prototype work is active; the status page distinguishes progress from final acceptance. No release dates are promised.

1. Establish the core

The initial foundations cover persistent state, bounded mutation preparation, journal integrity and protocol framing. The initial compile failure was repaired in P00; integration and current verification remain required for each accepted behavior.

Acceptance requires more than individually correct modules: a durable owner must validate a change, synchronize the exact intent and publish it without creating an ambiguous successful outcome.

2. Deliver ordinary database work

Add document models, optional schemas, usable CRUD, predicates, indexes, property edges and bounded traversal. Preserve missing/null distinctions, precise numeric behavior and clear mutation errors.

Acceptance requires a working local interface with atomic transactions, stable query views and documented resource limits. Document model · Queries and graphs.

3. Connect a real application

Use RURAL as an application's actual transactional backend in an isolated profile. Connect project, task, governance and decision records. Add workspace manifests and recoverable coordination with Git worktrees.

Acceptance requires visible application behavior, preserved source authority and correct operation across restart. A query mirror or successful import alone does not complete this stage.

4. Connect the sky and Oracle

Accept source-bound website events, product analytics and business facts. Implement correction-aware metrics and the Oracle's compact, authorized query/evidence flow through MCP.

Acceptance includes deduplication, report replacement, late data, source coverage and useful answers from the real consumer. Any token-saving claim needs an equivalent-answer baseline and measured usage.

5. Complete local operational safety

Verify backup/restore, retained roots, bounded merges, deletion behavior, concurrent readers and mixed workloads. Publish an honest local walkthrough and an acceptance record for the exact build.

This is the gate for a usable local alpha.

6. Advance to a single server

The next product milestone introduces restricted forms/event intake, Linux validation, disk-scale analytical storage, explicit workload budgets and the transport/security work needed for public exposure.

Clustering and federation follow separate decisions about ownership, quorum, failure domains and cross-partition consistency. A single server reachable worldwide is not a globally resilient database.

The status page remains the authority for which gates have actually passed.