The Sovereign Substrate

This document specifies the Sovereign Substrate architecture at conformance depth and documents the reference implementation that conforms to it. It is the technical companion to the principal paper The Sovereign Substrate: A constitutional architecture for governed computation (S. Wheeler, v2.0, 2026), which develops the structural problem and the constitutional argument.

The architecture admits three primitive types (functional, state, and credential units) composing under eight protocol mechanisms specified at the depth required to write a conforming implementation: compile-at-commit, roll-up under strictest-binding-wins, wilful inclusion, refusal under non-reconcilable composition, runtime evaluation against the compiled form, the uniform invalidation surface, administrative acts on the ledger, and federation of archives under multi-custodian quorum. The compositional vocabulary is uniform across scales: the same primitives describe governance at a single functional unit, an institutional substrate, and a cooperative substrate of sovereigns.

The reference implementation is a working artefact, not a thought experiment, and includes twelve end-to-end demonstrations against substantively different problems. The paper exhibits three at sufficient depth to show the mechanisms composing: Robodebt (runtime policy refusal), the Boeing 737 MAX MCAS failure (certification as a substrate pattern), and the 2012 JPMorgan Chase London Whale loss (the densest single composition of mechanisms).

Six architectural commitments are named as not yet substantiated by the prototype. Each mechanism's bounded claims are specified alongside the mechanism, with the architecture's limits (adversarial gaming, refusal cost, centralising effects under adoption) named where the mechanism is specified rather than relegated to a separate section. The architecture is what this document specifies; the protocol is what conforming implementations satisfy; the substrate is what an operator runs. The technical primitives are not novel; the architectural commitments at conformance depth, exercised against working code, are.