diff --git a/landing/index.html b/landing/index.html index bcaf3d3..1c7b9d3 100644 --- a/landing/index.html +++ b/landing/index.html @@ -4,14 +4,14 @@
Speckl is a multi-agent software development system where the primary artifact is the specification, not the code. Every behavior traces back to its source of intent — automatically.
- -Speckl is an open standard for specification-first development with dark provenance. It defines how to write what a system should do — in a machine-verifiable format — before any code is written. Every behavior traces back to its source of intent.
+ +Speckl is not a product or a platform. It is a methodology and language specification, published freely under MIT. The SpeckDL language, the Dark Provenance methodology, and the reference implementations define the standard. Products built on it — compilers, verification tools, compliance APIs — will come as the ecosystem grows.
+Write what your system should do in SpeckDL, a constraint-based specification language. Z3 proves your specs are consistent before any code exists.
+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.
Every function, every branch, every side effect links back to its source — a regulation, a design decision, a conversation. Invisible until needed, always complete.
+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.
Orchestrator, team leads, and SMEs collaborate on specs. The harness scales automatically under load. No human coordination required.
+Minimal reference tools for SpeckDL parsing, Z3 constraint verification, and provenance graph generation. The building blocks for tooling, not a production system.
Speckl targets DO-178C, IEC 62304, ISO 26262, FDA 21 CFR 820. Compliance is structural, not bolted-on.
+The standard is the foundation. Consulting, SaaS tooling, and compliance APIs will build on it — validated through real-world use before they ship.
Consulting: Hands-on engagements with regulated-industry teams.
SaaS: Spec editor, live Z3 verification, provenance graph browser.
Compliance API: Audit reports, traceability matrices.