What is written, stays written.

What it is

A foundation to build a storage product on.

Wyrd is the layer a mid-sized cloud provider could build a worldwide storage product on — a Drive-like service, an S3-compatible object store, or the backend for a collaborative editor. It keeps metadata and bulk data architecturally separate, yet every write commits as a single, indivisible act: from the caller’s point of view, a write either happened in full or not at all.

The model follows the Colossus-class lineage — a global control plane over per-zone storage, with bulk data flowing directly between client and storage servers so throughput scales with the fleet rather than through a bottleneck. One static binary on a laptop for development; a multi-region deployment in production. The same system, configured differently.

Why it exists

The combination is the gap.

Plenty of systems do part of this. Few combine all of it: a rigorous atomic commit point, a globally consistent namespace, erasure coding within a zone and geo-replication across zones, pluggable metadata and chunk backends behind narrow interfaces, an on-disk format specified so the data outlives the software that wrote it — and correctness treated as the headline feature, verified with deterministic simulation testing from day one.

• atomicCommit-point atomicity. A write is linearized at a single point. No torn state, no half-written files, ever observable.
• globalOne namespace, many zones. A strongly consistent global directory tree; per-file writes linearize at a home zone.
• durableConfigurable per zone. Replication or Reed-Solomon erasure coding within a zone; whole-copy geo-replication across them.
• pluggableNarrow backends. Embedded store for development, distributed store for production — behind the same interface.
• provableCorrectness as a feature. Deterministic simulation testing: every bug reproduces from a seed.

The Norns

Three keepers, named for what they tend.

In myth, the three Norns weave fate — what has been, what is, and what is owed. Wyrd borrows them for the parts of the system that carry real weight, so each component’s name states its job.

The name

Wyrd — the woven whole.

A storage system is, in the end, a keeper of wyrd: it holds what was written, weaves in what is being written, and carries the debts of what it still owes. The whole woven state is the Wyrd; the Norns are the ones who tend it. The Norns weave the Wyrd.