XIOM project -- experimental, pre-alpha

OrbitDB

An embedded database engine in pure XIOM: B-tree index, write-ahead log, query engine, transactions and crash recovery, organised as a layered engine on the shared durable-systems substrate. It reuses the ecosystem's core primitives instead of copying them.

Status: the repository is private during development, so there are no downloads and no release claims yet. Every state below points at evidence in the private repository; nothing is said here that the repository does not show.

Package: xiom.orbitdb -- the embedded engine, codename Satellite (live on the registry, incubating).
Standalone: Station -- the PostgreSQL-class server tier with standalone releases (pending).

What works today

Verified on Windows and WSL: conformance 160/160, crash recovery 25/25, fuzz and soak green. Pinned to the official v0.64.5 toolchain; readiness is scored 77.5/100 in the repository's production-readiness record.

B-tree index

Insert, search and delete on a flat-array B-tree, churn-proven against a model.

Range queries

Low/high scans, min/max and in-order traversal.

Write-ahead log

Append, replay and truncate; durable segment file.

Crash recovery

Disk WAL and page file with crash harnesses on Windows and WSL (25/25 on both); torn-tail healing.

Query engine

Equality and range filters with limit and offset.

Schema catalog

Schema definitions with validation.

Pages and buffer pool

Storage primitives, page files and the buffer pool; the v2 byte container is the default (v1 auto-detected, migrates on write).

Tuple codec and CRC32C

Byte-packed records; checksums verified on read.

Conformance suite

160/160 checks on Windows and WSL.

Transactions

State machine only -- no isolation or crash-safe redo/undo yet.

fsync durability

The standard library's fsync and sync-write primitives landed and now back ORBITDB's durable log path; the remaining steps are the power-loss test matrix and the pager.

What is next

Two-tier direction: the embedded engine (Satellite) continues as the release line while a server tier (Station) is planned on the same engine; Station v1 is trusted-network/local-only until the TLS server side lands (both tiers pre-alpha today).

Pager next (the current storage milestone), then a refactor pass, then the Station prerequisites.
Phase 2: GitHub releases and mirror installers, once the repository opens and the gates pass.

Pre-alpha means pre-alpha: the engine's core, durable log and pages work today, but nothing here is ready for production data.

Downloads

Nothing to download yet. Phase 2 publishes GitHub releases and mirror installers for every OS, like the toolchain's.