Reference implementation

Status

Scaffolding, not protocol. No released library, no wire-compatible peer, and no protocol logic behind the traits. It claims no conformance module, because a claim it cannot yet be held to would be worse than no claim.

A Rust workspace, developed alongside the specification. Its purpose so far has been to find out whether the specification can be implemented at all — which is why the parts that exist are the parts that were in doubt.

What exists

Crate	What it is
sovm-host	The host interface as traits. The contract SOP/1 needs from SSP/1, expressed so an alternative host can satisfy it
sovm-mls-provider	The OpenMLS provider a node runs — the crypto and storage seam MLS requires
sovm-iroh	The SOVM-IROH binding. The first protocol code in the workspace, and the crate the binding’s decision gates were measured against
sovm-sequencer-model	An executable model of the blind commit sequencer, which reproduces the coordination findings the specification records
sovm-conformance	The corpus loader and runner: it executes the published vectors and enforces their traceability to the specification

Modules claimed

None. The conformance clause requires an implementation to state its module set, and a set this workspace could satisfy today would be empty of everything except the floor it does not yet implement either.

Corpus result

sovm-conformance runs the SOP/1 corpus green, which is a statement about the corpus rather than about the protocol: the cases it executes pin registry literals, deterministic CBOR, BLAKE3 identifiers, frame construction and the transport binding — the parts that are settled enough to have exact bytes.

The harness also enforces the properties that keep the corpus honest: every case’s specification anchor must resolve, every gate it names must exist, and every quoted normative fragment must appear verbatim in the section it cites. A section that moves without the corpus following it fails the harness.

Not implemented

Everything else. There is no change-event apply path, no domain-key hierarchy, no object plane, no mailbox, and no peer to talk to. The status page lists the ten gates that stand between this and a production protocol; none has passed.