Run what ships. Watch what is landing.
Statecraft is built in the open, one milestone at a time. Two things run today on their own: the governance toolchain and the substrate. The control plane that ties them into one loop is landing rung by rung, and every step below links to the spec that governs it.
$ cargo install spec-spine-cliRunnable today
Govern a corpus with spec-spine
spec-spine is the one piece the whole family is built on, and it runs today. Point it at a directory of markdown specs and it compiles a typed registry, indexes your code, lints the corpus, and refuses code that drifts from its owning spec. This website is one of its governed corpora.
$ cargo install spec-spine-cliRun the enrahitu substrate
enrahitu is the EnRaHiTu template chassis a stamped app is born from, and it is runnable on its own: Encore.ts, rauthy, hiqlite, and Turso in a single container with zero managed dependencies. Clone it and follow its README to bring the container up.
$ git clone https://github.com/statecrafting/enrahituOn the ladder
Stamp an app from the template contract
plannedThe stamp produces a complete application from the enrahitu chassis, born with a certificate that binds an explicit agentic posture. The chassis ships today; the template contract that drives the stamp is still being finalized, so a self-serve stamp is not a documented path yet. Follow the contract in the registry.
Self-host the control plane
plannedStatecraft, the control plane, is AGPL-3.0 and designed to be self-hostable. Standing up a self-hosted plane is itself an in-progress milestone; the home page status ladder rolls up exactly how far it has come, straight from the specs. The self-host path will be documented here when it ships.
Where next?
The status ladder on the home page is authoritative for how far each rung has come; it rolls up straight from the specs on every deploy.