Tools for governed software work
Make intent
a working contract.
Software changes quickly. Authority should stay legible. Statecraft connects authored specifications, bounded local work and evidence you can inspect.
The working model
Separate the acts.
Keep the record.
A proposed design, an approved contract, implemented code and a qualified deployment answer different questions. The family keeps those distinctions visible.
Write the desired behavior and its limits in an authored specification. A proposal remains draft until its owner approves it.
Read the public source context →Where to begin
Three ways into the family.
A family, with boundaries.
Local work, specification authority, Rust applications, memory and evidence primitives.
Meet the products ↗02 / THE CONTRACTSInspect the public record.
Lifecycle, implementation, ownership and provenance, linked to immutable source revisions.
Browse the catalog ↗03 / THE DESIGNRead the reasoning.
A current introduction to intent, authority and evidence, with interactive architecture notes.
Read the paper ↗