Documentation
What RURAL is, how it works and how far it has got. Every page states its status: aim, design, in development or tested today.
30 documents
Start here 5
Introduction
One engine for typed queries, flexible documents, relationships, exact values and retained history.
Why RURAL
The visible-world whitepaper: philosophy, proposed architecture and explicit delivery boundaries.
Development setup
The repository developer workflow, compiler, guarded build and verification commands.
Project status and limits
The current capability map, scoped evidence and explicit non-claims.
Roadmap
The native prototype acceptance gates and the evidence still required.
Data and workspaces 7
Documents, models and CRUD
Ordinary records and optional schemas are the starting point for every RURAL workload.
SQL, typed queries and graph views
Typed query evaluation, graph relations, retained snapshots, cursors and bounded COUNT.
Numeric values and RAM
Exact integer key-values, expiry, ownership and the ephemeral RAM boundary.
Embedding and application workflows
The embedded directory API, owned outcomes and current evidence boundaries.
Snapshots and branches
Explore independent branches while sharing unchanged state and preserving current authority.
Analytics and warehouse
Current analytics facts, typed metrics and explicit source coverage.
Oracle and MCP
The local MCP query and replacement-view polling subset, with unsupported Oracle operations.
Operations 3
Durability and recovery
The single-owner local journal, append and sync semantics, and bounded tail recovery.
Security model
Scoped read-only grants, current authority and revocation boundaries.
Backup and portability
Define what a complete database backup must preserve and what remains outside it.
Internals 4
Architecture overview
The proposed branching-world architecture, concurrent readers, intake and explicit security and performance limits.
Persistent map
How immutable AVL roots share nodes and values across snapshots without parent-chain reads.
Prepared state engine
Atomic byte-record batches, branch heads, scoped receipts and allocation-free publication.
Journal and framing
The local journal's ownership, sequence and integrity rules, with clear format boundaries.
Reference 4
Local development protocol
Authenticated local HTTP admission and the shared document service contract.
Dependency contract
The current runtime dependency boundary and historical adoption record.
Root 2.1 kernel API
The frozen 34-symbol ABI 1.4 caller contract, refusal codes and process-crash durability limits.
Changelog
Current repository changes and dated development checkpoints.
Research and evidence 2
Whitepaper 5
Storage, execution and distribution for a visible world
Storage, transactions, recursive branches, capacity, recovery and upgrades.
Privacy, identity and the loom
Post-quantum design, private discovery, messaging, keys and the limits of authority.
The visible world: crystals, computation and earned value
Geometry, language understanding, an operational observatory and typed economic contracts.
RURAL that keeps running
Morpheus research and how RURAL could keep serving across independent operators.
Agent wallets and accountable settlement
Agent budgets, funded credits, real-money claims and accountable batching of external settlement.
No matching documents
Try a shorter word, such as "branch", "journal" or "security".