Introduction

Status: Development. RURAL is an in-progress database prototype. The version badge follows the repository's version file; project status explains what is implemented and what is still being checked.

RURAL is a database project written in Zig. It is being built to store documents, connect related records, and let people try changes on separate branches.

The goal starts with familiar database work. Create a project. Update a task. Define a model. Connect a decision to the documents that support it. Query those records, keep a consistent snapshot and explore a different course of action in an independent branch.

Keep related records together

A project can include tasks, decisions and supporting documents. You can connect those records, query them, and keep a consistent view while other changes are made. Source files remain under the authority of their existing tools; RURAL is designed for records owned by the application using it.

Why branching matters

A workspace can start from an existing world, make changes and branch again. Unchanged data is shared through immutable roots. Each branch owns its later writes, while readers can retain an earlier view.

That foundation supports experiments with code, operational plans and data without copying the entire database for every variation. Merging, working-copy coordination and authority inheritance still require explicit rules. Explore worlds and branches.

Read the status labels

• Foundation identifies implemented low-level components and their documented boundaries.

• Design describes the intended product contract and acceptance work ahead.

• Development covers evolving interfaces, setup and the current project state.

RURAL is an independent database design. It does not promise compatibility with another database's query language or claim another product's benchmark results.

Start with documents and CRUD, then read the architecture and current limits.