A constraint-based specification language that defines what a system does, not how. Specs are small, stable, and machine-verifiable — the audit surface for regulated systems.
A methodology where every behavior traces back to its source — a regulation, a design decision, a conversation. The provenance graph is always present, materialized on demand for audits or debugging.
Minimal reference tools for SpeckDL parsing, Z3 constraint verification, and provenance graph generation. The building blocks for tooling, not a production system.
The standard is the foundation. Consulting, SaaS tooling, and compliance APIs will build on it — validated through real-world use before they ship.
Specs are orders of magnitude smaller than the code they generate. They change less often. The audit surface stays tractable.
If Speck→WASM compilation preserves semantics, human review at the spec boundary satisfies assurance requirements.
Agents generate code. Humans own specifications. The chain of custody for intent stays intact.