Readers get a stable world.
Immutable roots establish a precise view of data. Long-running analysis should operate outside the mutation critical section, with explicit limits on retained snapshots and work.
RURAL / ARCHITECTUREFROM FIRST PRINCIPLES
Good roots.
Room to grow.
A deliberate foundation for connected data. Immutable roots, explicit transactions, durable history and bounded interfaces.
Read the technical guideSYSTEM MAP / DESIGN OVERVIEWREAD TOP TO BOTTOM
One local foundation first. Distribution follows its own correctness and operational gates.
This map combines implemented foundations and planned integration. Individual documents identify their current status.
RESTART / RECOVERY WALKTHROUGH
ILLUSTRATIVE SEQUENCERecover to the last verified boundary.
See how a snapshot and journal can restore a committed view. The example exposes an incomplete tail instead of treating it as accepted state.
VERIFIED SNAPSHOTS8root r₈ · sequence 008
APPENDED JOURNAL FRAMES
009validcommit
010validcommit
011incomplete tailnot replayed
RESTORED ROOTr₈sequence 008
RECOVERY CHECKPOINT
Start from the verified snapshot.
Load snapshot S8 and verify its contents before replaying later frames.
- Validate framing and checksums
- Replay only complete accepted records
- Report the recovered sequence clearly
- Load and verify snapshot S8 at sequence 008.
- Validate journal frames 009 and 010; identify frame 011 as incomplete.
- Replay complete accepted records through sequence 010.
- Report restored root r₁₀ and the excluded incomplete tail. Actual recovery guarantees depend on the documented filesystem and fault model.
THE CHOICES THAT SHAPE THE SYSTEM
Explicit, all the way down.
Persistent map
Changes have a clear order.
Mutations need an accountable commit boundary. The local architecture begins with an ordered owner; independent writers and distributed transactions require additional coordination.
Durability has to be earned.
Checksums, frame validation and replay are building blocks. A durable database also needs filesystem behavior, fault tests and a recovery contract that match its acknowledgement promises.
History doesn’t rewind authority.
A historical snapshot is a data view. It must not revive a revoked credential, activate an old effect or turn a branch into a way around current permissions.
A DELIBERATE DEPENDENCY BOUNDARYBuilt with Zig.
Built with Zig.
Built to be understood.
First-party prototype code uses Zig. Pinned third-party dependencies are permitted, with explicit ownership, licenses and replacement boundaries. RURAL keeps its own storage engine; this website uses a separate Go + HTMX stack.
Read the contractDATABASE DEVELOPMENT / RURALStart with the
Start with the
current foundation.
Explore the design.
Check the implementation status.